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

Information Disclosure in github.com/fleetdm/fleet/v4 (CVE-2026-48786)

Summary

Vulnerability in github.com/fleetdm/fleet/v4 (CVE-2026-48786). Confidential information can be exposed externally. Exploitable via POST /api/latest/fleet/targets. Mitigation: upgrade to 4.87.0 or later.

Original description

The description as published by the source.

Summary

The target search endpoint (POST /api/latest/fleet/targets) returned team enroll secrets and full team configuration, including credential-bearing agent options, to observer-class users. Other team-facing endpoints mask these fields for observers; the target search endpoint did not apply the same sanitization.

Impact

An authenticated user with Observer, Observer+, or Technician role (global or team-scoped) could retrieve unmasked team enroll secrets and team agent options by performing a target search against an observer-runnable query.

With a leaked team enroll secret, an attacker could enroll unauthorized hosts into the affected team. If the team's agent options contained credentials such as AWS secret access keys or proxy passwords, those values were also exposed.

Patches

  • v4.87.0

Workarounds

If an immediate upgrade is not possible, administrators should:

  • Rotate team enroll secrets for any team that may have been exposed
  • Rotate any credentials stored in team agent options (AWS keys, proxy passwords, session tokens)
  • Restrict Observer and Technician roles to fully trusted users until the patch is applied

Credits

Fleet thanks @fuzzztf for responsibly reporting this issue.

For more information

If there are any questions or comments about this advisory:

Send an email to security@fleetdm.com
Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel…

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-48786 has been found in github.com/fleetdm/fleet/v4.
Attackers can target a specific entry point like POST /api/latest/fleet/targets 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.87.0 or later.
If unsure, ask your IT team or search "github.com/fleetdm/fleet/v4 CVE-2026-48786" on the vendor's site.

CVE-2026-48786 (github.com/fleetdm/fleet/v4) — CWE-200 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/latest/fleet/targets
Patched: 4.87.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.

❓ What is the problem

Information disclosure (CWE-200) exists in github.com/fleetdm/fleet/v4. Attackers reach the vulnerable code path via POST /api/latest/fleet/targets.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/fleetdm/fleet/v4. Attack surface: POST /api/latest/fleet/targets.

🔥 Severity

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

🔧 How to fix

Update to 4.87.0.

🛡️ 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 POST /api/latest/fleet/targets 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 'POST /api/latest/fleet/targets' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

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

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

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/latest/fleet/targets 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.87.0"}]}]

References

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