CVE-2026-22808: Fleet Windows MDM endpoint has a Cross-site Scripting vulnerability

Published Jan 20, 2026
·
Updated

Summary

A cross-site scripting (XSS) vulnerability in Fleet’s Windows MDM authentication flow could allow an attacker to compromise a Fleet user account. In certain cases, this could lead to administrative access and the ability to perform privileged actions on managed devices.

Impact

If Windows MDM is enabled, an attacker could exploit a cross-site scripting (XSS) vulnerability by convincing an authenticated Fleet user to visit a malicious link. Successful exploitation could allow retrieval of the user’s Fleet authentication token from their browser.

A compromised authentication token may grant administrative access to the Fleet API, allowing an attacker to perform privileged actions such as deploying scripts to managed hosts.

This issue does not allow unauthenticated access and does not affect instances where Windows MDM is disabled.

Patches

- 4.78.2 - 4.77.1 - 4.76.2 - 4.75.2 - 4.53.3

Workarounds

If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.

For more information

If you have any questions or comments about this advisory:

Email us at security@fleetdm.com Join #fleet in osquery Slack

Credits

We thank @secfox-ai for responsibly reporting this issue.

Other sources

fleetdm/fleet is open source device management software. Prior to versions 4.78.2, 4.77.1, 4.76.2, 4.75.2, and 4.53.3, if Windows MDM is enabled, an unauthenticated attacker can exploit this XSS vulnerability to steal a Fleet administrator's authentication token (FLEET::authtoken) from localStorage. This could allow unauthorized access to Fleet, including administrative access, visibility into device data, and modification of configuration. Versions 4.78.2, 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.

MITRE

Affected Software

10 affected componentsFixes available
go/github.com/fleetdm/fleet/v4<4.43.5-0.20260111020427-0e6c790803d1
4.43.5-0.20260111020427-0e6c790803d1
go/github.com/fleetdm/fleet>=4.75.0<4.75.2
4.75.2
go/github.com/fleetdm/fleet>=4.76.0<4.76.2
4.76.2
go/github.com/fleetdm/fleet>=4.77.0<4.77.1
4.77.1
go/github.com/fleetdm/fleet>=4.78.0<4.78.2
4.78.2
fleetdm fleet<4.53.3
fleetdm fleet>=4.75.0<4.75.2
fleetdm fleet>=4.76.0<4.76.2
fleetdm fleet>=4.78.0<4.78.2
fleetdm fleet=4.77.0

Event History

Jan 20, 2026
Advisory Published
via GitHub·08:52 PM
Data Sourced
via GitHub·08:52 PM
DescriptionWeaknessAffected Software
Jan 21, 2026
CVE Published
via MITRE·09:18 PM
Data Sourced
via MITRE·09:18 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
Affected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-22808?

CVE-2026-22808 is classified as a medium severity cross-site scripting vulnerability that could compromise user accounts in Fleet's Windows MDM.

2

How do I fix CVE-2026-22808?

To fix CVE-2026-22808, upgrade to Fleet versions 4.43.5, 4.75.2, 4.76.2, 4.77.1, or 4.78.2 as specified in the remedy section.

3

What versions of Fleet are affected by CVE-2026-22808?

CVE-2026-22808 affects Fleet versions prior to 4.43.5, as well as versions 4.75.0 to 4.75.2, 4.76.0 to 4.76.2, 4.77.0 to 4.77.1, and 4.78.0 to 4.78.2.

4

What can an attacker do with CVE-2026-22808?

An attacker exploiting CVE-2026-22808 could potentially compromise a Fleet user account, leading to unauthorized access and control.

5

Is CVE-2026-22808 specific to a certain platform?

Yes, CVE-2026-22808 specifically affects Fleet’s Windows MDM environment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203