What is CVE-2026-54245?

CVE-2026-54245 is a high-severity SQL injection vulnerability in github.com/fleetdm/fleet (go), affecting versions < 4.86.2. It is fixed in 4.86.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

Which versions of github.com/fleetdm/fleet are affected by CVE-2026-54245?

github.com/fleetdm/fleet (go) versions < 4.86.2 is affected.

Is there a fix for CVE-2026-54245?

Yes. CVE-2026-54245 is fixed in 4.86.2. Upgrade to this version or later.

Is CVE-2026-54245 exploitable, and should I be worried?

Whether CVE-2026-54245 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-54245 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-54245 in github.com/fleetdm/fleet

Q: Which versions of github.com/fleetdm/fleet are affected by CVE-2026-54245?

github.com/fleetdm/fleet (go) versions < 4.86.2 is affected.

Q: Is there a fix for CVE-2026-54245?

Yes. CVE-2026-54245 is fixed in 4.86.2. Upgrade to this version or later.

Q: Is CVE-2026-54245 exploitable, and should I be worried?

Whether CVE-2026-54245 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-54245 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-54245?

Upgrade github.com/fleetdm/fleet to 4.86.2 or later.

Summary

Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database

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.

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.

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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Affected versions

github.com/fleetdm/fleet (< 4.86.2)

Security releases

github.com/fleetdm/fleet → 4.86.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/fleetdm/fleet to 4.86.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-54245? CVE-2026-54245 is a high-severity SQL injection vulnerability in github.com/fleetdm/fleet (go), affecting versions < 4.86.2. It is fixed in 4.86.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
Which versions of github.com/fleetdm/fleet are affected by CVE-2026-54245? github.com/fleetdm/fleet (go) versions < 4.86.2 is affected.
Is there a fix for CVE-2026-54245? Yes. CVE-2026-54245 is fixed in 4.86.2. Upgrade to this version or later.
Is CVE-2026-54245 exploitable, and should I be worried? Whether CVE-2026-54245 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-54245 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-54245? Upgrade github.com/fleetdm/fleet to 4.86.2 or later.