/

CVE-2026-23998

Severity:

HIGH RISK

(7.5)

Improper Certificate Validation in Fleet Windows MDM

CVE-2026-23998

Analyzed

Vulnerability type

Category:

Improper Certificate Validation

CWE:

CWE-295

Impact:

Impersonation and Sensitive Configuration Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Fleet's Windows MDM management endpoint contains an issue where some requests can be processed without validating the client's TLS certificate, weakening mutual TLS (mTLS) protections.

Under specific conditions, an attacker who knows a valid enrolled device identifier could impersonate that device and obtain sensitive configuration payloads intended for it.

Affected context

The vulnerability occurs in Fleet deployments that:

  • Use the Windows MDM management endpoint
  • Rely on mutual TLS (mTLS) client certificates for device authentication
  • Accept and process Windows MDM management requests over TLS

In affected versions, requests that omit or fail to present a valid client certificate may still be treated as trusted under certain paths or conditions, allowing the server to associate them with an existing enrolled Windows device.

Exploit preconditions

  • Attack surface: Fleet Windows MDM management endpoint exposed over the network (typically HTTPS).
  • Required access: Network-level ability to send requests to the Windows MDM endpoint; prior knowledge of a valid enrolled device identifier.
  • Trigger point: Submission of crafted MDM management requests that omit or bypass client certificate presentation while referencing an enrolled device.
  • Why exploitation is possible: The mTLS enforcement logic does not consistently verify the presence and authenticity of client certificates before associating a request with a device record, allowing unauthenticated requests to be mapped to an existing device identity.

Why this happens

This issue stems from incomplete or inconsistent enforcement of mTLS client certificate validation on the Windows MDM management endpoint.

Although the design expects each enrolled device to authenticate using a client certificate, some code paths treat requests as trusted even when no valid certificate is presented or validated.

This maps to CWE-295: Improper Certificate Validation, where the application relies on mutual TLS but fails to reliably confirm that clients have presented a valid, trusted certificate before associating them with a device identity or authorizing access to configuration data.

Potential impact

  • An attacker could impersonate a specific enrolled Windows device and retrieve its MDM configuration payloads.
  • Sensitive configuration data, such as Wi-Fi or VPN settings, certificates, or other secrets delivered via MDM profiles, could be exposed.
  • Attackers may use disclosed secrets to further compromise the targeted Windows device's network environment (e.g., accessing protected Wi-Fi or VPN resources).
  • Configuration integrity for the impersonated device could be undermined if future logic relies on similar trust assumptions.

General mitigation guidance

Effective mitigation focuses on strengthening certificate-based authentication and reducing the trust boundary around device identifiers:

  • Ensure that all endpoints relying on mTLS enforce strict client certificate validation, including presence, chain of trust, and binding to device identities.
  • Treat device identifiers as untrusted input and require successful certificate validation before associating requests with any enrolled device record.
  • Apply defense-in-depth by introducing additional checks (such as per-device tokens, binding configuration to certificate fingerprints, or short-lived device credentials) rather than relying solely on identifiers that can be guessed or observed.
  • Limit the sensitivity of data delivered through MDM profiles where possible, and compartmentalize secrets so a single device's configuration leak has constrained blast radius.
  • Regularly review authentication and authorization paths for management endpoints to ensure consistent enforcement of TLS and certificate policies.

How teams detect issues like this

Organizations can detect and monitor for this class of issue using:

  • Static analysis rules that flag TLS/mTLS endpoints where client certificate validation is optional, conditional, or bypassable.
  • Code review checklists that explicitly require verification of ClientAuth configurations, certificate checks, and binding logic between certificates and device identities.
  • Integration or security tests that attempt to access MDM or management endpoints without client certificates, confirming consistent rejection.
  • Runtime monitoring and logging that records whether incoming MDM requests presented a client certificate, along with device identifiers, allowing anomaly detection and retrospective analysis.
  • Policy enforcement (e.g., infrastructure-as-code checks) to ensure TLS configurations are defined with strict client certificate requirements on all device-management endpoints.

Sources

SourceLink
github.comgithub.com/fleetdm/fleet/releases/tag/fleet-v4.81.0
github.comgithub.com/fleetdm/fleet/security/advisories/GHSA-2rc4-7jc6-qffh

Frequently asked

questions

Yes, it can be exploited remotely by any party that can reach the Windows MDM management endpoint over the network, provided they also know a valid enrolled device identifier.

The attacker needs network access to the Fleet Windows MDM endpoint and prior knowledge of a legitimate enrolled device identifier. No valid client certificate is required in the vulnerable configuration.

The safest pattern is to enforce strict, mandatory client certificate validation on all mTLS-protected endpoints and to ensure that device identities are only established after a successful certificate check, with clear binding between certificates and device records.

Future prevention involves standardizing mTLS usage patterns, introducing automated checks for certificate enforcement, treating identifiers as untrusted until authenticated, and adding security tests that verify endpoints reject requests lacking valid client certificates.

Find out what's already
exploitable in your codebase.