CriticalGHSA-63m5-974w-448vCVE-2026-23518GO-2026-4335

Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment

Published 20 Jan 2026 · Updated 28 Feb 2026

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

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 packages

Affected
>=4.78.0 <4.78.3
Fixed in
4.78.3
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet@v4.78.3
Affected
>=4.77.0 <4.77.1
Fixed in
4.77.1
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet@v4.77.1
Affected
>=4.76.0 <4.76.2
Fixed in
4.76.2
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet@v4.76.2
Affected
>=4.75.0 <4.75.2
Fixed in
4.75.2
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet@v4.75.2
Affected
<4.43.5-0.20260112202845-e225ef57912c
Fixed in
4.43.5-0.20260112202845-e225ef57912c
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet@v4.43.5-0.20260112202845-e225ef57912c

Details

Summary

A vulnerability in Fleet’s Windows MDM enrollment flow could allow an attacker to submit forged authentication tokens that are not properly validated. Because JWT signatures were not verified, Fleet could accept attacker-controlled identity claims, enabling enrollment of unauthorized devices under arbitrary Azure AD user identities.

Impact

If Windows MDM is enabled, an attacker can enroll rogue devices by submitting a forged JWT containing arbitrary identity claims. Due to missing JWT signature verification, Fleet accepts these claims without validating that the token was issued by Azure AD, allowing enrollment under any Azure AD user identity.

Patches

  • 4.78.3
  • 4.77.1
  • 4.76.2
  • 4.75.2
  • 4.53.3

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-63m5-974w-448v 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, and gives you the command that fixes it.

More advisories for github.com/fleetdm/fleet

  • HighCVE-2026-54245Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database · 20 Aug 2026
  • HighCVE-2026-23517Fleet has an Access Control vulnerability in debug/pprof endpoints · 20 Jan 2026
  • MediumCVE-2026-22808Fleet Windows MDM endpoint has a Cross-site Scripting vulnerability · 20 Jan 2026
github.com/fleetdm/fleet security overview

References

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