Advisory

GHSA-ffg9-j72f-j6xm

Also known as: CVE-2026-24899, GO-2026-5358

Summary

Fleet Windows MDM Azure AD JWT Authentication Bypass

Details

Summary

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.

Impact

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.

Workarounds

If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.

For more information

If you have any questions or comments about this advisory:
Email us at [[email protected]](mailto:[email protected])
Join #fleet in osquery Slack

Credits

We thank @zaddy6 for responsibly reporting this issue.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-05-14 13:13 UTC
Modified
2026-06-25 19:56 UTC

Affected packages and fixes

github.com/fleetdm/fleet/v4

Go · All systems

Affected

  • introduced 0, fixed 4.82.0 (semver)

Fixed versions

4.82.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences