CVE-2026-22808: Fleet Windows MDM endpoint has a Cross-site Scripting vulnerability
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
- Fixed version: github.com/fleetdm/fleet (Go) 4.75.2, 4.76.2, 4.77.1; github.com/fleetdm/fleet/v4 (Go) 4.75.2, 4.76.2, 4.77.1.
Low priority for now. Upgrade to github.com/fleetdm/fleet (Go) 4.75.2, 4.76.2, 4.77.1; github.com/fleetdm/fleet/v4 (Go) 4.75.2, 4.76.2, 4.77.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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::auth_token) 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.
- Published
- Jan 21, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-79
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| fleetdm | fleet | cpe:2.3:a:fleetdm:fleet |
Limit the impact of XSS
This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.
Check security headersAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fleetdm fleetbefore 4.53.3
- fleetdm fleet4.75.0 and later · before 4.75.2
- fleetdm fleet4.76.0 and later · before 4.76.2
- fleetdm fleet4.78.0 and later · before 4.78.2
- fleetdm fleet4.77.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
fleetdm fleet
- >= 4.78.0, < 4.78.2, >= 4.77.0, < 4.77.1, >= 4.76.0, < 4.76.2, < 4.53.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/fleetdm/fleet | from 4.75.0 · before 4.75.2 | 4.75.2 |
| Go | github.com/fleetdm/fleet | from 4.76.0 · before 4.76.2 | 4.76.2 |
| Go | github.com/fleetdm/fleet | from 4.77.0 · before 4.77.1 | 4.77.1 |
| Go | github.com/fleetdm/fleet | from 4.78.0 · before 4.78.2 | 4.78.2 |
| Go | github.com/fleetdm/fleet/v4 | from 4.75.0 · before 4.75.2 | 4.75.2 |
| Go | github.com/fleetdm/fleet/v4 | from 4.76.0 · before 4.76.2 | 4.76.2 |
| Go | github.com/fleetdm/fleet/v4 | from 4.77.0 · before 4.77.1 | 4.77.1 |
| Go | github.com/fleetdm/fleet/v4 | from 4.78.0 · before 4.78.2 | 4.78.2 |
| Go | github.com/fleetdm/fleet/v4 | before 4.43.5-0.20260111020427-0e6c790803d1 | 4.43.5-0.20260111020427-0e6c790803d1 |
Same product
fleetdm: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-26276SAML authentication vulnerability in Fleet40Plan
- CVE-2026-103264Fleet before 4.87.0 Authentication Bypass via Device Identifiers37Monitor
- CVE-2026-23518Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-24841Apr 18, 2022 · Improper Authorization in github.com/fleetdm/fleet32Monitor
- ← EarlierCVE-2025-27509Mar 6, 2025 · SAML authentication vulnerability due to improper SAML response validation37Monitor
- Later →CVE-2026-23517Jan 21, 2026 · Fleet has an Access Control vulnerability in debug/pprof endpoints25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/fleetdm/fleet | 4.75.2 | Package registry (OSV) |
| Go:github.com/fleetdm/fleet | 4.76.2 | Package registry (OSV) |
| Go:github.com/fleetdm/fleet | 4.77.1 | Package registry (OSV) |
| Go:github.com/fleetdm/fleet | 4.78.2 | Package registry (OSV) |
| Go:github.com/fleetdm/fleet/v4 | 4.43.5-0.20260111020427-0e6c790803d1 | Package registry (OSV) |
| Go:github.com/fleetdm/fleet/v4 | 4.75.2 | Package registry (OSV) |
| Go:github.com/fleetdm/fleet/v4 | 4.76.2 | Package registry (OSV) |
| Go:github.com/fleetdm/fleet/v4 | 4.77.1 | Package registry (OSV) |
| Go:github.com/fleetdm/fleet/v4 | 4.78.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.