CVE-2026-24899: fleetdm fleet · Authentication Bypass by Spoofing
Affects fleetdm fleetSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 4.82.0 soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.82.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:NExploitation evidence
Disclosed: evidence found.
CVE published 14 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade fleet and fleetdm/fleet to 4.82.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| fleetdmfleet | Affected
| Fixed in
|
GitHubfleetdm/fleetpkg:github/fleetdm/fleetOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch addressing this vulnerability is available in Fleet version 4.82.0. Users should upgrade to this version to remediate the issue. For those unable to upgrade immediately, temporarily disabling Windows MDM is recommended to prevent exploitation. Since Fleet is a cloud service, the vendor manages remediation for the cloud-hosted service; users should consult the vendor advisory for confirmation and further guidance.
Description
Fleet versions prior to 4.82.0 have an authentication bypass vulnerability in the Windows MDM enrollment flow. The software accepts Azure AD tokens from any tenant because it validates JWT signatures using Microsoft's multi-tenant JWKS endpoint but does not enforce audience or issuer claims. This flaw allows attackers with access to any Azure AD tenant to use valid Microsoft-signed tokens to enroll unauthorized devices and interact with Fleet's MDM APIs. Sensitive enrollment secrets may be exposed during device management. Version 4.82.0 includes a patch that addresses this issue. Users unable to upgrade immediately should disable Windows MDM as a temporary mitigation.