CVE-2026-24899
HighSummary
In the Fleet device management software, prior to version 4.82.0, a vulnerability in the Windows MDM enrollment flow allows authentication tokens from any Azure AD tenant to be accepted. The issue arises from the lack of enforcement of the `aud` and `iss` claims in JWT signatures.
Risk Assessment
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. This could lead to the exposure of sensitive enrollment secrets.
Recommendation
It is recommended to immediately upgrade to version 4.82.0, which contains a patch. If an upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
Other vulnerabilities in Fleet device management software
Original NVD description (English source)
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.