Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.6amended

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

CVE-2026-54245GHSA-7q96-f8xw-jv5j

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/fleetdm/fleet/v4 4.86.2; github.com/fleetdm/fleet 4.86.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-54245: 0.57% estimated exploitation activity in the next 30 days; percentile 47.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-7q96-f8xw-jv5j

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6264

  4. Revision 1 · created ·

    Published from osv record GHSA-7q96-f8xw-jv5j

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54245

Advisory: Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database
IDs: CVE-2026-54245, GHSA-7q96-f8xw-jv5j
Record: https://patchnext.com/advisories/cve-2026-54245 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fleetdm/fleet/v4 4.86.2; github.com/fleetdm/fleet 4.86.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fleetdm/fleet/v4: affected < 4.86.2; fixed in 4.86.2
- Go github.com/fleetdm/fleet: affected < 4.86.2; fixed in 4.86.2

## Suggested inspection (read-only)
- Go github.com/fleetdm/fleet/v4: check the installed version with your package manager.
- Go github.com/fleetdm/fleet: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fleetdm/fleet/v4, github.com/fleetdm/fleet.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7q96-f8xw-jv5j (OSV record GHSA-7q96-f8xw-jv5j lists affected ranges: Go github.com/fleetdm/fleet >=0 <4.86.2 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6264 (OSV record GO-2026-6264 lists affected ranges: Go github.com/fleetdm/fleet/v4 >=0 <4.86.2 (fixed))
- Verified: https://github.com/advisories/GHSA-7q96-f8xw-jv5j (GitHub-reviewed advisory GHSA-7q96-f8xw-jv5j lists affected ranges: Go github.com/fleetdm/fleet >=0 <4.86.2)

Commands are suggestions: review each one before running it.

Loading voting…