CVE-2026-54245: SQL Injection
Summary
A SQL injection vulnerability in Fleet's Okta conditional access integration could allow an attacker who controls a single enrolled host to read or modify arbitrary data in the Fleet database, including stored session tokens. Disclosed session tokens may be replayed to act as a global administrator, which on a managed fleet leads to remote code execution on enrolled hosts.
Impact
When Fleet Premium with Okta conditional access is configured, an unauthenticated request path that supports the conditional access integration uses a host-supplied value in a database query without proper parameterization. Because the value is reported by the host's own agent and stored verbatim, any party that controls one enrolled host (the lowest-privilege role in the product) can influence the query.
Successful exploitation could allow:
- Disclosure of arbitrary database contents, including credentials and session tokens. - Replay of disclosed session tokens to gain global administrator access. - Subsequent actions available to a global administrator, including running scripts on enrolled hosts.
This issue requires Fleet Premium with the Okta conditional access integration enabled. It does not affect instances where Okta conditional access is not configured.
Workarounds
If an immediate upgrade is not possible, disable the Okta conditional access integration until the patched version is deployed.
For more information
If you have any questions or comments about this advisory:
Email us at security@fleetdm.com
Join #fleet in osquery Slack
Credits
We thank @fuzzztf for responsibly disclosing this issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/fleetdm/fleetto a version that resolves this vulnerability.Fixed in 4.86.2 - Configuration
If an immediate upgrade is not possible, disable the Okta conditional access integration until the patched version is deployed.
Fleet Okta conditional access integration enabled = false
Event History
Frequently Asked Questions
Which Fleet deployments are affected?
The issue requires Fleet Premium with the Okta conditional access integration enabled. Deployments without that integration configured are not described as affected.
What does an attacker need to exploit this issue?
An attacker needs control of one enrolled host, the product's lowest-privilege role. The vulnerable request path is unauthenticated, but exploitation relies on a host-supplied value reported by that host's agent.
What could an attacker do after exploitation?
They could read or modify arbitrary Fleet database data, including stored session tokens. A disclosed token could be replayed for global administrator access, which can include running scripts on enrolled hosts.