Is CVE-2026-24899 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-24899 being exploited in the wild.

How severe is CVE-2026-24899?

High severity, with a CVSS score of 7.5, published 14 May 2026.

Which products and versions are affected?

github.com/fleetdm/fleet/v4 (Go) < 4.82.0, SEMVER:introduced=0,fixed=4.82.0.

Is there a fix for CVE-2026-24899?

Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.82.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-24899 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-24899?

Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-24899: Fleet Windows MDM authentication bypass via Azure AD JWT spoofing

Q: Is there a fix for CVE-2026-24899?

Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.82.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-24899 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-24899?

Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-24899 · Severity: high · CVSS 7.5 · Published 2026-05-14

Fleet is an open-source platform used by IT and security teams to manage and monitor laptops and servers. A security flaw in the Windows device enrollment process allows unauthorized users to bypass authentication by using identity tokens from any Microsoft Azure AD account, not just the one belonging to the organization. This could allow an attacker to enroll unauthorized devices into the company's management system and potentially access sensitive configuration secrets.

Technologies: github.com/fleetdm/fleet/v4 (Go). Vendors: Go.

Quick answers

Is CVE-2026-24899 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-24899 being exploited in the wild.
How severe is CVE-2026-24899?: High severity, with a CVSS score of 7.5, published 14 May 2026.
Which products and versions are affected?: github.com/fleetdm/fleet/v4 (Go) < 4.82.0, SEMVER:introduced=0,fixed=4.82.0.
Is there a fix for CVE-2026-24899?: Yes. github.com/fleetdm/fleet/v4 (Go): upgrade to 4.82.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-24899 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-24899?: Check whether you run github.com/fleetdm/fleet/v4 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/fleetdm/fleet/v4 (Go): upgrade to 4.82.0 or later
```
go get github.com/fleetdm/fleet/v4@v4.82.0
```

Technical details

An authentication bypass exists in Fleet's Windows MDM enrollment flow prior to version 4.82.0. While Fleet validates JSON Web Token (JWT) signatures using Microsoft's multi-tenant JWKS endpoint, it fails to enforce the 'aud' (audience) or 'iss' (issuer) claims. Consequently, any valid Microsoft-signed Azure AD access token with the required scopes can be used to authenticate to Fleet's MDM endpoints. An attacker can exploit this to enroll rogue devices or interact with MDM management APIs, potentially exposing sensitive enrollment secrets within MDM command payloads. The issue is resolved in version 4.82.0 by allowing administrators to specify allowed Entra (Azure AD) tenant IDs.

Affected products

Fleet Device Management (fleetdm) Fleet < 4.82.0

Identifiers

CVE-2026-24899
GHSA-ffg9-j72f-j6xm
GO-2026-5358

Timeline

2026-03-12: patched: Version 4.82.0 released
2026-05-13: advisory: Vendor security advisory published
2026-05-14: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.