Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database
Published 20 Aug 2026 · Updated 26 Aug 2026
Is your project on an affected github.com/fleetdm/fleet?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <4.86.2
- Fixed in
- 4.86.2
go get github.com/fleetdm/fleet@v4.86.2Details
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](mailto:security@fleetdm.com)
Join #fleet in osquery Slack
Credits
We thank @fuzzztf for responsibly disclosing this issue.
Is GHSA-7q96-f8xw-jv5j in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fleetdm/fleet, and gives you the command that fixes it.
More advisories for github.com/fleetdm/fleet
- CriticalCVE-2026-23518Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment · 20 Jan 2026
- HighCVE-2026-23517Fleet has an Access Control vulnerability in debug/pprof endpoints · 20 Jan 2026
- MediumCVE-2026-22808Fleet Windows MDM endpoint has a Cross-site Scripting vulnerability · 20 Jan 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.