Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-46371 medium CVSS 6.5

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

Summary

SQL injection in github.com/fleetdm/fleet/v4 (CVE-2026-46371). Confidential information can be exposed externally. Exploitable via GET /api/v1/fleet/mdm/apple/commands. Mitigation: upgrade to 4.84.2 or later.

Original description

The description as published by the source.

Summary

A vulnerability in Fleet's Apple MDM commands listing endpoint allowed authenticated users with the lowest-privilege Observer role to extract sensitive values from joined database tables — including host enrollment secrets and Apple Push Notification Service (APNS) tokens — through a cursor-based binary search oracle. The endpoint accepted a user-supplied order_key parameter that was not validated against a column allowlist.

Impact

The GET /api/v1/fleet/mdm/apple/commands endpoint constructs its query using a deprecated helper that did not restrict which columns could appear in the ORDER BY clause. The underlying query joins the hosts and nano_enrollments tables, so any column on those tables could be supplied as order_key. An attacker with Observer credentials could then use the cursor-based pagination parameter (after) to binary-search the value of the chosen column one character at a time. The targeted values never appeared in the response body, but the presence or absence of results revealed each character.

With extracted node_key or orbit_node_key values, an attacker could impersonate enrolled hosts to Fleet's osquery and Orbit endpoints, submit fabricated host data, and retrieve pending scripts and commands. The APNS values are exploitable only by a party that also possesses the organization's APNS certificate.

Exploitation required authenticated Observer access and a Fleet deployment with Apple MDM enabled and at least one queued…

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-46371 has been found in github.com/fleetdm/fleet/v4.
Attackers can target a specific entry point like GET /api/v1/fleet/mdm/apple/commands over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade github.com/fleetdm/fleet/v4 to 4.84.2 or later.
If unsure, ask your IT team or search "github.com/fleetdm/fleet/v4 CVE-2026-46371" on the vendor's site.

CVE-2026-46371 (github.com/fleetdm/fleet/v4) — CWE-89 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/fleet/mdm/apple/commands / order_key / hosts / nano_enrollments
Patched: 4.84.2 — apply immediately
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/v4. Attackers reach the vulnerable code path via GET /api/v1/fleet/mdm/apple/commands.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/fleetdm/fleet/v4. Attack surface: GET /api/v1/fleet/mdm/apple/commands / order_key / hosts / nano_enrollments.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.84.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/v1/fleet/mdm/apple/commands requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/fleetdm/fleet/v4' . 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/v4' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/v1/fleet/mdm/apple/commands' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/v1/fleet/mdm/apple/commands への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/fleetdm/fleet/v4 to 4.84.2

    ステージング環境で 4.84.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /api/v1/fleet/mdm/apple/commands on staging to confirm patch closes the vector

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

Affected packages

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

References

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