| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/fleetdm/fleet | ≥ 4.75.0, < 4.75.2≥ 4.76.0, < 4.76.2≥ 4.77.0, < 4.77.1≥ 4.78.0, < 4.78.3< 4.43.5-0.20260112202845-e225ef57912c | 4.75.24.76.24.77.14.78.34.43.5-0.20260112202845-e225ef57912c |
| github.com/fleetdm/fleet/v4 | ≥ 4.75.0, < 4.75.2≥ 4.76.0, < 4.76.2≥ 4.77.0, < 4.77.1≥ 4.78.0, < 4.78.3 | 4.75.24.76.24.77.14.78.3 |
| fleet | = 4.77.0≥ 4.75.0, < 4.75.2≥ 4.76.0, < 4.76.2≥ 4.78.0, < 4.78.3< 4.53.3 | 4.75.24.76.24.78.34.53.3 |
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.
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.
If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
If you have any questions or comments about this advisory:
Email us at [email protected] Join #fleet in osquery Slack
We thank @secfox-ai for responsibly reporting this issue.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free