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

> SQL injection in Fleet Premium's Okta integration allows host-controlled database compromise, leading to admin access and remote code execution.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-7q96-f8xw-jv5j, GO-2026-6264

## What is CVE-2026-54245?

CVE-2026-54245 is a high-severity SQL injection vulnerability in fleetdm fleet, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Fleet is an open-source device management platform built on osquery. In versions prior to 4.86.2, the Okta conditional access integration in Fleet Premium is vulnerable to SQL injection through a host-supplied value that is used in a database query without proper parameterization, allowing an attacker who controls a single enrolled host to read or modify arbitrary data in the Fleet database. The value is reported by the host's own agent and stored verbatim, then used on an unauthenticated request path that supports the conditional access integration, so any party controlling one enrolled host, the lowest-privilege position in the product, can influence the query. By disclosing arbitrary database contents an attacker can extract stored session tokens and replay them to act as a global administrator, and on a managed fleet that administrator access enables running scripts on enrolled hosts, leading to remote code execution. The issue requires Fleet Premium with the Okta conditional access integration enabled and does not affect instances where it is not configured. This issue is fixed in version 4.86.2.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-54245?

3 open source packages ship an affected version, including github.com/fleetdm/fleet and github.com/fleetdm/fleet/v4.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/fleetdm/fleet` | Go | All versions | 4.86.2 |
| `github.com/fleetdm/fleet` | Go | All versions | 4.86.2 |
| `github.com/fleetdm/fleet/v4` | Go | All versions | 4.86.2 |

## How do I fix CVE-2026-54245?

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

## Is CVE-2026-54245 being exploited?

There is no known exploitation of CVE-2026-54245 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54245 and fix it if it is affected.

What it is: CVE-2026-54245 is a high-severity SQL injection vulnerability in fleetdm fleet, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54245 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fleetdm/fleet (Go): affected all versions; fixed in 4.86.2
- github.com/fleetdm/fleet (Go): affected all versions; fixed in 4.86.2
- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.86.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54245/ (Markdown: https://insights.sbomify.com/CVE-2026-54245/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54245
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54245
- OSV: https://osv.dev/vulnerability/CVE-2026-54245

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54245/
Summaries are generated and may contain mistakes; the official description above is the record.