# Fleet Windows MDM Azure AD JWT Authentication Bypass

Advisory record · `GHSA-ffg9-j72f-j6xm`

- **Identifiers:** `GHSA-ffg9-j72f-j6xm` · `CVE-2026-24899` · `GO-2026-5358`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-290](https://cwe.mitre.org/data/definitions/290.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 14 May 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/fleetdm/fleet/v4` (Go): affected `<4.82.0`; fixed in `4.82.0`

## 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

- 8.2 High, CVSS 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`, from 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

- 31 Oct 2026, 15:07 UTC: First seen by agentprime
- 31 Oct 2026, 15:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-ffg9-j72f-j6xm)

## Sources

- [GitHub Advisory Database: GHSA-ffg9-j72f-j6xm](https://github.com/advisories/GHSA-ffg9-j72f-j6xm)
- [OSV: GHSA-ffg9-j72f-j6xm](https://osv.dev/vulnerability/GHSA-ffg9-j72f-j6xm)
- <https://github.com/fleetdm/fleet/security/advisories/GHSA-ffg9-j72f-j6xm>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-24899>
- <https://github.com/fleetdm/fleet>
- <https://github.com/fleetdm/fleet/releases/tag/fleet-v4.82.0>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-ffg9-j72f-j6xm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ffg9-j72f-j6xm/>. Everything for agents: <https://agentprime.io/llms.txt>.
