Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment
fleetdm fleet
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fleetdm/fleet Go |
|
|
fleetdm fleet
| Product | Affected | Fixed in |
|---|---|---|
| github.com/fleetdm/fleet Go |
|
|
4.75.24.43.5-0.20260112202845-e225ef57912c| github.com/fleetdm/fleet/v4 Go |
|
|
Fleet is open source device management software. In versions prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.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. Versions 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 fix the issue. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
From the CVE record · GitHub_M
Fleet’s Windows MDM enrollment flow did not verify JWT signatures. An attacker who submits a forged authentication token during enrollment could enroll an unauthorized device under an arbitrary Azure AD user identity. The input does not specify whether prior authentication is required.
Teams running Fleet versions before the applicable fixes—4.78.3, 4.77.1, 4.76.2, 4.75.2, or 4.53.3—or using affected github.com/fleetdm/fleet Go packages should check their deployments.