CVE-2026-54245
CVE-2026-54245 is a remote code execution vulnerability in github.com/fleetdm/fleet. O3 Security confirms whether CVE-2026-54245 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database
Real-World Exposure
github.com/fleetdm/fleetReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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 [email protected]
Join #fleet in osquery Slack
Credits
We thank @fuzzztf for responsibly disclosing this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/fleetdm/fleet | all versions | 4.86.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/fleetdm/fleet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/fleetdm/fleet to 4.86.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54245 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-54245 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-54245. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-54245 in your dependencies?
O3 detects CVE-2026-54245 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.