On this page (8 sections)

A critical authentication bypass, tracked as CVE-2026-130759, affects Fleet versions from 4.71.0 before 4.88.2. According to the NVD record, the SAML single sign-on (SSO) callback looks up sessions using client-supplied identifiers that are never validated, which opens a path to logging in as a global admin.

If you run a self-managed Fleet server with SAML SSO enabled, particularly one where many people can run live queries or hold enroll secrets, you should check your version now. The research available so far comes from a single record, so some details (such as exploitation status) are not yet known.

At a glance

What happened

The vulnerability was published on 2026-11-18. Per the NVD description, a flaw in the SAML SSO callback lets users who can run live queries or enroll secret holders plant attacker-controlled identity provider metadata in the session store. They can then present a self-signed SAML response and be logged in as a global admin.

A vendor advisory is referenced on GitHub (GHSA-94f5-6j6w-r3rh). The research provided here does not include its full text, so check it directly for the vendor's own wording, workarounds and credits.

Technical details in plain terms

SAML SSO works by trusting a signed statement from your identity provider (IdP) that says who a user is. The security of the whole scheme depends on the application checking that the signature comes from the IdP you configured, and not from anyone else.

Here, the callback looks up sessions using identifiers supplied by the client without validating them. That lets an attacker influence which IdP metadata is used for verification. If the verifying metadata is attacker-controlled, a self-signed response passes as valid. This is consistent with the weakness class CWE-347, a failure to properly verify a cryptographic signature.

The attack is not anonymous. The description says it involves users able to run live queries or enroll secret holders. That narrows the realistic attacker pool to insiders, compromised low-privilege accounts, or anyone holding an enroll secret. The result is still severe: a global admin account on a device management platform.

Who is affected

  • Fleet servers running any version from 4.71.0 up to, but not including, 4.88.2.
  • Deployments where SAML SSO is in use. The research describes the flaw in the SAML SSO callback; it does not say whether servers without SSO are exposed, so confirm this in the vendor advisory.
  • Environments where many users can run live queries, or where enroll secrets are widely shared or stored in places that are easy to read.

A global admin takeover on a management server could expose data and controls across everything that server manages. The research does not describe specific post-compromise impact, so treat that as a reasonable concern rather than a confirmed outcome.

How to check your exposure

First find your Fleet server version. Confirm the exact method in Fleet's documentation for your install type, and compare the result with the affected range of 4.71.0 up to but not including 4.88.2.

Then review who holds the permissions the attack depends on. Look at the list of users who can run live queries and at where your enroll secrets are stored and shared.

Finally, review recent activity. Look in your Fleet audit or activity records and your IdP logs for unexpected global admin logins, logins that do not match an IdP sign-in event, or changes to SSO or IdP settings. The research does not describe specific indicators, so these are general review steps rather than known signatures of this attack.

What to do now

  1. Identify every Fleet server and note its version. Anything from 4.71.0 before 4.88.2 is affected.
  2. Upgrade to 4.88.2 or later, following Fleet's upgrade documentation and taking a backup first.
  3. Read the vendor advisory GHSA-94f5-6j6w-r3rh for workarounds, especially if you cannot upgrade immediately.
  4. Reduce who can run live queries and who knows your enroll secrets until you have patched.
  5. Rotate enroll secrets if there is any chance they were exposed to people who should not hold them.
  6. Review global admin accounts and recent admin logins; remove anything you do not recognize.
  7. Check the SSO configuration and stored IdP metadata for entries you did not set up.
  8. If you find signs of misuse, rotate API tokens and credentials that a global admin could reach, and follow your incident process.
Caution. Upgrading a management server can briefly interrupt the console and host check-ins. Schedule the change and take a backup of the database and configuration first.

Detection and monitoring afterwards

Where you can, keep Fleet behind a VPN or an IP allowlist so that the SSO callback is not reachable from the whole internet. Alert on new global admin accounts, role changes and SSO setting changes, and send Fleet logs to a central place where a compromised admin cannot erase them.

If your Fleet server is reachable over HTTPS on its own hostname, monitoring that hostname for certificate and DNS changes, for example with Webforta Monitor, helps you notice unexpected changes around the service, though it does not detect or prevent this vulnerability. You can also check the endpoint's TLS setup with the free SSL checker.

For broader reading on how application-layer filtering fits into a defense, see what a WAF is. A filter in front of a service does not replace patching, so upgrading remains the fix.

What is still unknown

  • Whether the flaw is being exploited. The research reports no exploitation and no CISA KEV entry, but absence of reports is not proof of safety.
  • Whether public proof-of-concept code exists. The research does not say.
  • Who assigned the 9.4 score and its full vector. Only the number and the critical rating are given.
  • Any vendor workaround. Check the GitHub advisory directly.
Only one independent publisher covers this story so far, and the facts above come from the NVD record. Details may be refined as the vendor advisory and other sources are analyzed.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-130759: 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…nvd.nist.gov ·
  • Fleet
  • SAML
  • SSO
  • authentication bypass
  • CVE-2026-130759