CVE
Fleet account takeover via case-insensitive token comparison
Affects Fleet versions before 4.92.0 that store authentication tokens in MySQL columns using the case-insensitive utf8mb4_unicode_ci collation. Fixed in 4.92.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.92.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.92.0.
Summary
Fleet versions before the fixed release accept security tokens for invites and email changes when the letter case is altered, so an attacker who holds one can reuse it. Remotely, without logging in or any action by the victim, that attacker can redirect the victim's email to take over the account or redeem invites with roles up to Global Admin.
Original description
Fleet before 4.92.0 contains an improper authentication vulnerability that allows attackers to reuse case-mutated security tokens because MySQL token columns used case-insensitive collation. Attackers holding a case-normalized invite or email-change token can redirect a victim's email for account takeover or redeem invites with roles up to Global Admin.
Who should check
Teams running Fleet (fleetdm, Go module github.com/fleetdm/fleet/v4) before 4.92.0, including anyone using invites, email changes, local MFA or device authentication.
“Affected versions < 4.92.0”
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Go packages
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.92.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130757 (Fleet before 4.92.0 Case-Insensitive Security Token Comparison Account Takeover), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130757 (entry last updated 2026-11-18):
Affected:
- Go package github.com/fleetdm/fleet/v4: fixed in 4.92.0
Fixed versions: 4.92.0.
Conditions (all must be true for the bug to be hit):
- Fleet versions before 4.92.0 with MySQL token columns using case-insensitive collation. (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-2r75-q53f-v8px)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130757 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130757 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fleetdm/fleet/security/advisories/GHSA-2r75-q53f-v8px
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130757
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130757"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
fixed in 4.92.0
No fix released. The advisory names 4.92.0 as the fix, which the registry doesn't have yet. The latest release, v4.43.4, is still affected.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · fleetdm/fleet · Advisory GHSA-2r75-q53f-v8px |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130757 |
| Record | NVD · CVE-2026-130757 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130757
Is CVE-2026-130757 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Several authentication-critical tokens in Fleet were stored in case-insensitive MySQL columns, so a token with altered letter case could match the real one. An attacker holding such a case-mutated token could redirect a victim's email to take over the account, or redeem invites with roles up to Global Admin. The highest-impact path is account takeover through the email-change flow.Source: github.com
Which versions are affected by CVE-2026-130757?
github.com/fleetdm/fleet/v4 (Go): before 4.92.0.Source: cve.now feed data
Am I affected, and how do I check?
Fleet versions before 4.92.0 with MySQL token columns that use the utf8mb4_unicode_ci collation. To check, look at the Fleet version reported by the server and the collation of the token columns in the MySQL database.Source: github.com
How do I fix CVE-2026-130757?
Upgrade Fleet to version 4.92.0 or later, which is the fixed version listed for this vulnerability. The sources name no vendor patch ids.Source: github.com