Skip to main content
Menu
CVEs

CVE

Fleet authentication bypass in SAML SSO callback

Affects Fleet servers with SAML SSO turned on, in versions 4.71.0 through 4.92.x before their fixes. Fixed in 4.88.2, 4.89.3, 4.90.3, 4.91.2, and 4.92.3.

CVE-2026-130759Published Updated Summary written by a model

9.4CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 4.88.2, 4.89.3, 4.90.3, 4.91.2, 4.92.3
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Fleet versions 4.71.0 through before 4.88.2 (and other listed affected ranges through 4.92.x before their patched versions). SAML SSO turned on in Fleet.

Summary

Fleet contains an authentication bypass in its SAML SSO callback that lets an attacker log in as a global admin. An attacker can reach it remotely with low-privilege access, such as a user who can run live queries or enroll secret holders, by planting their own identity provider metadata in the session store and presenting a self-signed SAML response.

Original description

Fleet from 4.71.0 before 4.88.2 contains an authentication bypass vulnerability in the SAML SSO callback that looks up sessions using unvalidated client-supplied identifiers. Users able to run live queries or enroll secret holders can plant attacker-controlled identity provider metadata in the session store, then present a self-signed SAML response to log in as a global admin.

Who should check

Teams running Fleet (fleetdm/fleet, Go) servers with SAML SSO turned on, including any with observer+ live query users or enroll secret holders.

“Fleet instances without SAML SSO are not affected.”

github.com

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity9.4/10CVSS 9.4
  • No patch0/5No signal

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Fleet versions 4.71.0 through before 4.88.2 (and other listed affected ranges through 4.92.x before their patched versions). SAML SSO turned on in Fleet.
  • Upgrade to a fixed version: 4.88.2, 4.89.3, 4.90.3, 4.91.2, 4.92.3.

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-130759 (Fleet from 4.71.0 before 4.88.2 SAML SSO Authentication Bypass via Session Store Keys), 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-130759 (entry last updated 2026-11-18):
Affected:
- Go package github.com/fleetdm/fleet: from 4.71.0, fixed in 4.88.2
- Go package github.com/fleetdm/fleet: from 4.89.0, fixed in 4.89.3
- Go package github.com/fleetdm/fleet: from 4.90.0, fixed in 4.90.3
- Go package github.com/fleetdm/fleet: from 4.91.0, fixed in 4.91.2
- Go package github.com/fleetdm/fleet: from 4.92.0, fixed in 4.92.3
Fixed versions: 4.88.2, 4.89.3, 4.90.3, 4.91.2, 4.92.3.
Conditions (all must be true for the bug to be hit):
- Fleet versions 4.71.0 through before 4.88.2 (and other listed affected ranges through 4.92.x before their patched versions). (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-94f5-6j6w-r3rh)
- SAML SSO turned on in Fleet. (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-94f5-6j6w-r3rh)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130759 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130759 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-94f5-6j6w-r3rh
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-130759
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-130759"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fleetdm/fleet · Advisory GHSA-94f5-6j6w-r3rh
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130759
RecordNVD · CVE-2026-130759

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130759

Is CVE-2026-130759 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?

A flaw in Fleet's SAML SSO authentication lets an attacker log in as a global admin via session store keys. Any user who can run live queries, even a team-scoped observer+, could become a global admin, and with Premium just-in-time provisioning on, an attacker could also create a new admin account.Source: github.com

Which versions are affected by CVE-2026-130759?

github.com/fleetdm/fleet (Go): from 4.71.0 before 4.88.2. github.com/fleetdm/fleet (Go): from 4.89.0 before 4.89.3. github.com/fleetdm/fleet (Go): from 4.90.0 before 4.90.3. github.com/fleetdm/fleet (Go): from 4.91.0 before 4.91.2. github.com/fleetdm/fleet (Go): from 4.92.0 before 4.92.3.Source: cve.now feed data

Am I affected, and how do I check?

Affected are Fleet 4.71.0 before 4.88.2, plus the 4.89.0, 4.90.0, 4.91.0, and 4.92.0 lines before their fixed versions, and only on servers with SAML SSO turned on. To check, look at the Fleet server version and whether SAML SSO is turned on in Fleet's settings.Source: github.com

How do I fix CVE-2026-130759?

Upgrade to the fixed version for the release line in use: 4.88.2, 4.89.3, 4.90.3, 4.91.2, or 4.92.3.Source: github.com

More CVEs