Fleet has a Windows MDM management endpoint authentication bypass
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- None
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-295.
Summary
Fleet is open source device management software. Prior to version 4.81.0, a vulnerability in Fleet’s Windows MDM management endpoint could allow requests to be processed without proper client certificate validation. In certain circumstances, this could allow an attacker to impersonate an enrolled Windows device and retrieve sensitive configuration data. Fleet’s Windows MDM management endpoint relies on mutual TLS (mTLS) client certificates to authenticate enrolled devices. In affected versions, requests that did not present a client certificate could be incorrectly treated as trusted. As a result, an attacker with prior knowledge of a valid enrolled device identifier could potentially impersonate that device and receive configuration payloads intended for it. These payloads may contain sensitive information such as Wi-Fi or VPN configuration data, certificates, or other secrets delivered through MDM profiles. This issue does not allow enrollment of new devices, administrative access to Fleet, or compromise of the Fleet control plane. Impact is limited to the targeted Windows device. Version 4.81.0 contains a patch. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| fleetdm | fleet | before 4.81.0 | 4.81.0 | Patch available | CNA |
| — | github.com/fleetdm/fleet/v4 (Go) | before 4.81.0 | 4.81.0 | Patch available | GHSA-2rc4-7jc6-qffh |
- fleet Vendorfleetdm Affected before 4.81.0 Fixed in 4.81.0 Patch available CNA
- github.com/fleetdm/fleet/v4 (Go) Vendor— Affected before 4.81.0 Fixed in 4.81.0 Patch available GHSA-2rc4-7jc6-qffh
Remediation
- Fix · CNA fleet (fleetdm) Fixed in 4.81.0
- Fix · GHSA-2rc4-7jc6-qffh github.com/fleetdm/fleet/v4 (Go) Fixed in 4.81.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-23998
- 2026-10-03 Alias added: GHSA-2rc4-7jc6-qffh
References
Advisory 2
More fleetdm Fleet vulnerabilities
- TI-2026-65639 Fleet before 4.87.0 Authentication Bypass via Device Identifiers CVSS 4.0CRITICAL 9.3
- TI-2026-18942 Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment CVSS 4.0CRITICAL 9.3
- TI-2020-16097 SAML authentication vulnerability in Fleet CVSS 3.1CRITICAL 10.0
- TI-2026-21066 Fleet server may terminate unexpectedly when handling certain gRPC requests CVSS 4.0HIGH 8.7
- TI-2026-21065 Fleet's unbounded request body read allows remote Denial of Service CVSS 4.0HIGH 8.7
- TI-2026-20084 Fleet Windows MDM Azure AD JWT Authentication Bypass CVSS 4.0HIGH 8.2
Sources
- CVE-2026-23998 · CVE Program
- CVE-2026-23998 · NVD
- FIRST EPSS
- GHSA-2rc4-7jc6-qffh · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences