← Back
CVE-2026-24899
high
CVSS 7.5
Vulnerability in github.com/fleetdm/fleet/v4 (CVE-2026-24899)
Summary
vulnerability in github.com/fleetdm/fleet/v4 (CVE-2026-24899). Confidential information can be exposed externally. Exploitable via ``aud``. Mitigation: upgrade to `4.82.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-24899** has been found in github.com/fleetdm/fleet/v4.
Attackers can target a specific entry point like ``aud`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade github.com/fleetdm/fleet/v4 to **4.82.0** or later.
If unsure, ask your IT team or search "github.com/fleetdm/fleet/v4 CVE-2026-24899" on the vendor's site.
CVE-2026-24899 (github.com/fleetdm/fleet/v4) — CWE-290 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `aud` / `iss`
Patched: `4.82.0` — apply immediately
Workaround: If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
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
**A vulnerability** (CWE-290) exists in github.com/fleetdm/fleet/v4. Attackers reach the vulnerable code path via ``aud`` without authentication.
📍 Affected scope
github.com/fleetdm/fleet/v4 — . Attack surface: `aud` / `iss`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.82.0**.
🛡️ Workaround
Workaround: If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.パッチが適用されるまでの応急処置として、If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/fleetdm/fleet/v4 to 4.82.0ステージング環境で 4.82.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/fleetdm/fleet/v4
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.82.0"}]}]