Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/fleetdm/fleet/releases/tag/fleet-v4.82.0
- https://github.com/fleetdm/fleet/security/advisories/GHSA-ffg9-j72f-j6xm
FAQ
What is CVE-2026-24899?
CVE-2026-24899 is a documented vulnerability. 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. B...
How severe is CVE-2026-24899?
CVSS scoring is not yet available for CVE-2026-24899. Check NVD for updates.
Is there a patch for CVE-2026-24899?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.