Advisory record · GHSA-ffg9-j72f-j6xm

Fleet Windows MDM Azure AD JWT Authentication Bypass

CVSS 8.2 HighEPSS 0.0038 · 32nd percentile

Published by the GitHub Advisory Database at 14 May 2026, 13:13 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/fleetdm/fleet/v4Go<4.82.04.82.0
Identifiers
GHSA-ffg9-j72f-j6xm · CVE-2026-24899 · GO-2026-5358
Weakness (CWE)
CWE-290
Published
14 May 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Fleet (Go module github.com/fleetdm/fleet/v4) versions before 4.82.0 are affected. Its Windows MDM enrollment flow does not enforce the audience or issuer claims on Azure AD tokens, so an attacker with access to any Azure AD tenant can obtain a valid Microsoft-signed token and use it to enroll unauthorized devices and call MDM management APIs, where sensitive enrollment secrets may be exposed. Upgrade to Fleet 4.82.0 or later; if that is not possible, disable Windows MDM.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 32nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.