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.
If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
If you have any questions or comments about this advisory:
Email us at [email protected]
Join #fleet in osquery Slack
We thank @secfox-ai for responsibly reporting this issue.
| Score | Percentile |
|---|---|
| 0.01% | 1.47% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 7.5 | 3.1 | — |
|
| 8.2 | 4.0 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-2rc4-7jc6-qffh ↗ |
| CVE | CVE-2026-23998 ↗ |
| CWE id | Name |
|---|---|
| CWE-295 | Improper Certificate Validation |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| go | github.com/fleetdm/fleet/v4 | < 4.81.0 | 4.81.0 | — |