HighGHSA-2rc4-7jc6-qffhCVE-2026-23998GO-2026-5002

Fleet has a Windows MDM management endpoint authentication bypass

Published 14 May 2026 · Updated 8 Jun 2026

Is your project on an affected github.com/fleetdm/fleet/v4?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<4.81.0
Fixed in
4.81.0
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet/v4@v4.81.0

Details

Summary

A vulnerability in Fleet’s Windows MDM management endpoint could allow requests to be processed without proper client certificate validation. In certain circumstances, this could allow an attacker to impersonate an enrolled Windows device and retrieve sensitive configuration data.

Impact

Fleet’s Windows MDM management endpoint relies on mutual TLS (mTLS) client certificates to authenticate enrolled devices. In affected versions, requests that did not present a client certificate could be incorrectly treated as trusted.

As a result, an attacker with prior knowledge of a valid enrolled device identifier could potentially impersonate that device and receive configuration payloads intended for it. These payloads may contain sensitive information such as Wi-Fi or VPN configuration data, certificates, or other secrets delivered through MDM profiles.

This issue does not allow enrollment of new devices, administrative access to Fleet, or compromise of the Fleet control plane. Impact is limited to the targeted Windows device.

Workarounds

If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.

For more information

If you have any questions or comments about this advisory:

Email us at [security@fleetdm.com](mailto:security@fleetdm.com) Join #fleet in osquery Slack

Credits

We thank @secfox-ai for responsibly reporting this issue.

Is GHSA-2rc4-7jc6-qffh in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fleetdm/fleet/v4, and gives you the command that fixes it.

More advisories for github.com/fleetdm/fleet/v4

  • LowCVE-2026-54245Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101047Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101046Fleet: ORDER BY column injection on activity list endpoints in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101046Fleet: ORDER BY column injection on activity list endpoints · 20 Aug 2026
  • MediumCVE-2026-101047Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs · 20 Aug 2026
  • LowCVE-2026-48786Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint in github.com/fleetdm/fleet · 18 Aug 2026
All 59 advisories for github.com/fleetdm/fleet/v4

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.