SQL Injection in Fleet (CVE-2026-101046)
Summary
SQL injection in Fleet (CVE-2026-101046). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/fleet/activities. Mitigation: upgrade to 4.89.0 or later.
Original description
The description as published by the source.
Fleet before 4.89.0 contains an SQL injection vulnerability in the activity list endpoints (GET /api/v1/fleet/activities and GET /api/v1/fleet/hosts/{id}/activities). The deprecated cursor-pagination helper appendListOptionsWithCursorToSQL interpolated the caller-supplied sort/order key into the SQL ORDER BY clause without an allowlist, so an authenticated user with read access to Activity could order results by arbitrary columns. The impact is read-only and bounded to columns on the activity_past table that are not otherwise returned in these responses (e.g. details), allowing their values to be inferred through the resulting sort order; there is no write access, privilege escalation, or reachability of node_key or other host-join columns through these endpoints. Fixed in 4.89.0, which removes the deprecated helper and passes the sort column through SanitizeColumn.
Source: NIST National Vulnerability Database 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-101046 has been found in Fleet.
Attackers can target a specific entry point like GET /api/v1/fleet/activities over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade Fleet to 4.89.0 or later.
If unsure, ask your IT team or search "Fleet CVE-2026-101046" on the vendor's site.
CVE-2026-101046 (Fleet) — CWE-89 / CVSS v3 3.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/fleet/activities / GET /api/v1/fleet/hosts/{id}/activities
Patched: 4.89.0 — 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.
SQL injection (CWE-89) exists in Fleet. Attackers reach the vulnerable code path via GET /api/v1/fleet/activities.
Check the vendor advisory for the affected versions of Fleet. Attack surface: GET /api/v1/fleet/activities / GET /api/v1/fleet/hosts/{id}/activities.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to 4.89.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/fleet/activities requests with malformed payloads or SQL meta-characters. Run grep -r '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
-
1Identify exposure identify
grep -r 'Fleet' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Fleetを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/fleet/activities' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/fleet/activitiesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Fleet to 4.89.0ステージング環境で 4.89.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/fleet/activities on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com