Security readout for executives and security teams
Plain-English summary
CVE-2026-23518 affects Fleet device management. In vulnerable versions, Fleet’s Windows MDM enrollment can accept forged Azure AD identity tokens because JWT signatures are not verified. An unauthenticated attacker could enroll unauthorized devices as arbitrary Azure AD users. This is high business urgency for organizations using Fleet Windows MDM.
Executive priority
Prioritize within the emergency patch window if Fleet manages Windows devices through MDM. The issue can undermine device enrollment trust and identity attribution, creating risk of unauthorized device management access. If Windows MDM is not enabled, validate quickly and schedule normal remediation.
Technical view
Fleet versions before 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 contain a CWE-347 JWT signature verification flaw in Windows MDM enrollment. The CVSS 4.0 score is 9.3. Network access, low complexity, no privileges, and no user interaction are required, per the provided CVSS vector.
Likely exposure
Exposure is limited to Fleet deployments running affected versions with Windows MDM enrollment enabled, especially Azure AD MDM enrollment flows. Fleet installations not using Windows MDM are less directly exposed based on the advisory description, but should still verify version and configuration.
Exploitation context
The sources describe a remote, unauthenticated authentication bypass during Windows MDM enrollment. They do not state active exploitation, and the CVE is not marked as CISA KEV in the provided data. Treat exploitability as serious due to the unauthenticated network attack conditions and identity-control impact.
Researcher notes
The root issue is missing JWT signature verification in Fleet’s Windows MDM enrollment path. The public bundle names the fixing commit and GitHub advisory, but does not provide evidence of exploitation in the wild. Avoid assuming broader Fleet authentication impact beyond the described Windows MDM enrollment flow.
Mitigation direction
- Upgrade Fleet to 4.78.3, 4.77.1, 4.76.2, 4.75.2, 4.53.3, or later applicable fixed release.
- If immediate upgrade is not possible, temporarily disable Windows MDM as Fleet advises.
- Review Fleet’s GitHub advisory for release-specific guidance and operational considerations.
Validation and detection
- Inventory Fleet server versions and compare against the affected version ranges.
- Confirm whether Windows MDM enrollment is enabled in Fleet.
- After upgrading, verify Fleet reports a fixed version.
- Review recent Windows MDM enrollments for unexpected devices or Azure AD user identities.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-23518 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fleetdm/fleet/security/advisories/GHSA-63m5-974w-448vCVE reference · x_refsource_CONFIRM
- https://github.com/fleetdm/fleet/commit/e225ef57912c8f4ac8977e24b5ebe1d9fd875257CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.