External risk intelligence

Fleet SAML Authentication Bypass Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130759

Fleet is an endpoint management platform that typically exposes a web-based interface and API for administrators to manage fleet assets. Given its role as a centralized management console, it is commonly deployed as an internet-facing or edge-reachable service to facilitate remote device management and administrative access.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a critical vulnerability in Fleet's SAML single sign-on (SSO) feature. An attacker could potentially bypass authentication to gain global administrator privileges by exploiting how the system handles session lookups and SAML responses. This could allow unauthorized access and control over managed endpoints.

  • Authentication bypass allows admin access.
  • Critical vulnerability in endpoint management software.
  • Confirm relevance and assess exposure risk.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by first gaining the ability to run live queries or enroll secret holders, allowing them to inject attacker-controlled metadata into the session store. Subsequently, the attacker can present a self-signed SAML response to bypass authentication and gain global administrator privileges.

  • Requires specific roles to alter session store.
  • Presents a crafted SAML response.
  • Leads to unauthorized global admin access.

Live Threat

Current exploitation, exposure, and threat context

The SAML Single Sign-On callback in Fleet could be exploited when supported by the advisory, allowing an attacker to bypass authentication. By manipulating session data with attacker-controlled identity provider metadata, an attacker could present a self-signed SAML response to gain administrative access. This could impact the confidentiality, integrity, and availability of the system and sensitive information when the advisory conditions are met.

  • System credentials and administrative access.
  • Unvalidated SAML callback lookup.
  • Unauthorized administrative control.

Operational Fix

Recommended remediation, mitigation, and detection steps

The affected technology, Fleet, is an endpoint management platform. Responsibility for addressing this vulnerability likely falls to application owners, platform teams, and security operations, depending on how Fleet is deployed and managed within your organization. The first critical step is to determine the scope of your Fleet deployment, assess its reachability and business criticality, and identify the accountable team or individual.

  • Determine Fleet deployment and reachability.
  • Verify affected user access and impact.
  • Coordinate remediation with vendor.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Fleet and how is it used?

Fleet is an open-source endpoint management platform designed to help organizations monitor and manage their devices. It provides a centralized console and API, enabling administrators to run queries across their fleet to gather configuration data, check security posture, and manage assets at scale.

What does CWE-347 mean for CVE-2026-130759?

CWE-347 refers to improper verification of cryptographic signatures. In the context of this CVE, it means the software's SAML authentication process fails to correctly validate the authenticity of the incoming login data. Because the system does not properly verify the signature of the SAML response, an attacker can submit a fraudulent, self-signed response to impersonate a global administrator.

How does an attacker trigger this bypass?

The attack requires two specific steps. First, an attacker must already have the capability to run live queries or enroll secret holders within the platform to plant malicious identity provider metadata into the session store. Simply accessing the login page without these specific, prior-established permissions will not trigger the vulnerability.

Is my Fleet instance at risk?

According to Halo Surface Signal, Fleet is typically deployed as an internet-facing or edge-reachable service to support remote management. If your instance is accessible over the internet, it is at higher risk. You should evaluate whether your deployment is exposed to external networks or restricted to internal users.

How should I respond to this advisory?

Start by identifying your organization's specific Fleet version to confirm if it falls within the 4.71.0 to 4.88.2 range. Once confirmed, coordinate with your platform or security team to restrict access if necessary while you prepare to update to a patched version provided by the vendor.

References