What’s Vulnerable › Vulnerabilities
CVE-2026-24899: Fleet Windows MDM Azure AD JWT Authentication Bypass
- Severity: high (CVSS 7.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.4% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-05-14 · updated 2026-10-26
- Weakness: CWE-290
Description
Fleet is open source device management software. Prior to version 4.82.0, a vulnerability in Fleet's Windows MDM enrollment flow allows authentication tokens from any Azure AD tenant to be accepted. Because Fleet validates JWT signatures using Microsoft's multi-tenant JWKS endpoint but does not enforce the `aud` (audience) or `iss` (issuer) claims, any Microsoft-signed Azure AD access token containing the expected scopes can be used to authenticate to Fleet's MDM endpoints. If Windows MDM is enabled, an attacker with access to any Azure AD tenant can obtain a valid Microsoft-signed token and use it to enroll unauthorized devices and interact with Fleet's MDM management APIs. During device management, Fleet may expose sensitive enrollment secrets embedded in MDM command payloads, enabling further unauthorized access. Version 4.82.0 contains a patch. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
Affected products
- fleetdm fleet: before 4.82.0 — fixed in 4.82.0
How to fix
Upgrade to a fixed version: fleetdm fleet 4.82.0. Check the vendor advisory for mitigations.
References
- https://github.com/fleetdm/fleet/releases/tag/fleet-v4.82.0
- https://github.com/fleetdm/fleet/security/advisories/GHSA-ffg9-j72f-j6xm
Get alerted when CVE-2026-24899 or the next vulnerability affects your stack