Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54245

SQL Injection in github.com/fleetdm/fleet (CVE-2026-54245)

Summary

SQL injection in github.com/fleetdm/fleet (CVE-2026-54245). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.86.2 or later.

Original description

The description as published by the source.

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

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54245 has been found in github.com/fleetdm/fleet.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/fleetdm/fleet to 4.86.2 or later.
If unsure, ask your IT team or search "github.com/fleetdm/fleet CVE-2026-54245" on the vendor's site.

CVE-2026-54245 (github.com/fleetdm/fleet) — CWE-89
Patched: 4.86.2 — apply immediately
Workaround: If an immediate upgrade is not possible, disable the Okta conditional access integration until the patched version is deployed.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in github.com/fleetdm/fleet.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/fleetdm/fleet.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.86.2.

🛡️ Workaround

Workaround: If an immediate upgrade is not possible, disable the Okta conditional access integration until the patched version is deployed.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/fleetdm/fleet' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/fleetdm/fleet' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/fleetdm/fleet を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    If an immediate upgrade is not possible, disable the Okta conditional access integration until the patched version is deployed.

    パッチが適用されるまでの応急処置として、If an immediate upgrade is not possible, disable the Okta conditional access integration until the patched version is deployed. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/fleetdm/fleet to 4.86.2

    ステージング環境で 4.86.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/fleetdm/fleet
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.86.2"}]}]
Go github.com/fleetdm/fleet/v4
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.86.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details