Fleet Windows MDM endpoint has a Cross-site Scripting vulnerability
Published 20 Jan 2026 · Updated 3 Feb 2026
Is your project on an affected github.com/fleetdm/fleet?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=4.78.0 <4.78.2
- Fixed in
- 4.78.2
go get github.com/fleetdm/fleet@v4.78.2- Affected
- >=4.77.0 <4.77.1
- Fixed in
- 4.77.1
go get github.com/fleetdm/fleet@v4.77.1- Affected
- >=4.76.0 <4.76.2
- Fixed in
- 4.76.2
go get github.com/fleetdm/fleet@v4.76.2- Affected
- >=4.75.0 <4.75.2
- Fixed in
- 4.75.2
go get github.com/fleetdm/fleet@v4.75.2- Affected
- <4.43.5-0.20260111020427-0e6c790803d1
- Fixed in
- 4.43.5-0.20260111020427-0e6c790803d1
go get github.com/fleetdm/fleet/v4@v4.43.5-0.20260111020427-0e6c790803d1Details
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](mailto:security@fleetdm.com) Join #fleet in osquery Slack
Credits
We thank @secfox-ai for responsibly reporting this issue.
Is GHSA-gfpw-jgvr-cw4j in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fleetdm/fleet, and gives you the command that fixes it.
More advisories for github.com/fleetdm/fleet
- HighCVE-2026-54245Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database · 20 Aug 2026
- CriticalCVE-2026-23518Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment · 20 Jan 2026
- HighCVE-2026-23517Fleet has an Access Control vulnerability in debug/pprof endpoints · 20 Jan 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.