CVE-2026-23518
Unknown Unknown - Not Provided
JWT Signature Bypass in Fleet Windows MDM Enables Unauthorized Enrollment

Publication date: 2026-01-21

Last updated on: 2026-02-27

Assigner: GitHub, Inc.

Description
Fleet is open source device management software. In versions prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3, a vulnerability in Fleet's Windows MDM enrollment flow could allow an attacker to submit forged authentication tokens that are not properly validated. Because JWT signatures were not verified, Fleet could accept attacker-controlled identity claims, enabling enrollment of unauthorized devices under arbitrary Azure AD user identities. Versions 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 fix the issue. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-21
Last Modified
2026-02-27
Generated
2026-06-16
AI Q&A
2026-01-22
EPSS Evaluated
2026-06-15
NVD
CVE-2026-23518
Affected Vendors & Products
Showing 5 associated CPEs
Vendor Product Version / Range
fleetdm fleet to 4.53.3 (exc)
fleetdm fleet From 4.75.0 (inc) to 4.75.2 (exc)
fleetdm fleet From 4.76.0 (inc) to 4.76.2 (exc)
fleetdm fleet 4.77.0
fleetdm fleet From 4.78.0 (inc) to 4.78.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-347 The product does not verify, or incorrectly verifies, the cryptographic signature for data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Fleet's Windows MDM enrollment flow where attacker-submitted forged authentication tokens are not properly validated. Specifically, JWT signatures were not verified, allowing attackers to submit attacker-controlled identity claims. This flaw enables unauthorized devices to be enrolled under arbitrary Azure AD user identities.

Impact Analysis

The vulnerability can allow attackers to enroll unauthorized devices into the Fleet device management system under any Azure AD user identity. This could lead to unauthorized access, potential data breaches, and compromise of managed devices.

Mitigation Strategies

If an immediate upgrade to fixed versions (4.78.3, 4.77.1, 4.76.2, 4.75.2, or 4.53.3) is not possible, affected Fleet users should temporarily disable Windows MDM enrollment to mitigate the vulnerability.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-23518. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart