GHSA-63m5-974w-448v
Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Go | github.com/fleetdm/fleet | >= 4.78.0, < 4.78.3 | 4.78.3 |
| Go | github.com/fleetdm/fleet | >= 4.77.0, < 4.77.1 | 4.77.1 |
| Go | github.com/fleetdm/fleet | >= 4.76.0, < 4.76.2 | 4.76.2 |
| Go | github.com/fleetdm/fleet | >= 4.75.0, < 4.75.2 | 4.75.2 |
| Go | github.com/fleetdm/fleet | < 4.43.5-0.20260112202845-e225ef57912c | 4.43.5-0.20260112202845-e225ef57912c |
Details
As written in the advisory (Markdown source, shown as plain text).
### 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 [[email protected]](mailto:[email protected])
Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)
### Credits
We thank @secfox-ai for responsibly reporting this issue.
References
External links from the advisory. They lead to third-party sites.