External risk intelligence

Fleet Improper Authentication Allows Account Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-130757

Fleet is commonly deployed as an internet-facing fleet management and device security platform. As a centralized web-based application responsible for managing device infrastructure, it typically requires accessibility over the network to perform its core functions, placing its authentication and API endpoints in a position where they are often reachable from the internet in standard deployment patterns.

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

A vulnerability in Fleet software could allow attackers to hijack user accounts by reusing specially crafted security tokens, potentially granting them administrative access to managed devices. This issue arises from how the software handles token normalization, making it possible to exploit weakened tokens to impersonate legitimate users and gain control over sensitive information or systems.

  • Account takeover via reused, weakened security tokens.
  • Facilitates unauthorized administrative access to devices.
  • Confirm relevance and exposure for device management.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by obtaining a case-normalized invite or email-change token. This token can then be used to hijack a victim's account by redirecting their email or by redeeming the invite with elevated privileges, potentially up to Global Admin.

  • Attacker needs a specially crafted token.
  • Vulnerability triggered by token reuse.
  • Risk of account takeover and privilege escalation.

Live Threat

Current exploitation, exposure, and threat context

An improper authentication vulnerability in Fleet could allow an attacker to reuse case-mutated security tokens to redirect a victim's email for account takeover or redeem invites with elevated privileges, up to Global Admin, when supported by the advisory's conditions.

  • User account access.
  • Reused security tokens.
  • Account takeover or elevated privileges.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership

Given that Fleet manages device infrastructure, platform or infrastructure teams are likely responsible for its operational stability. The primary first step is to locate all Fleet instances, determine their business criticality and network exposure, and identify the accountable owner. Subsequently, a risk-based remediation plan can be developed, which may involve coordination with the vendor.

  • Identify Fleet instance owners and scope.
  • Verify if instances are externally reachable.
  • Plan remediation based on identified risk.

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 software?

Fleet is a platform designed for managing device infrastructure and security. It acts as a centralized web application, allowing organizations to monitor, secure, and manage fleets of devices by interacting with their systems through network-based APIs and web interfaces.

What does CVE-2026-130757 mean for security?

This CVE refers to an Improper Authentication vulnerability, specifically categorized as CWE-178 (Improper Handling of Case Sensitivity). Because the underlying MySQL database treated security tokens with case-insensitive collation, the system failed to distinguish between different token cases. This allows an attacker to reuse a manipulated token to impersonate a user or gain unauthorized administrative access.

How can an attacker trigger this vulnerability?

An attacker must possess a specially crafted invite or email-change token that has been case-normalized. If they provide this mutated token to the application, the system may incorrectly validate it as authentic. Note that this flaw is specific to token handling; standard operations that do not involve these specific token types are not the primary target of this mechanism.

Is my Fleet instance at risk?

According to Halo Surface Signal, Fleet is frequently deployed as an internet-facing platform to support its core device management functions. If your instance is reachable from the internet, it is more likely to be accessible to unauthorized parties. You should evaluate whether your deployment is exposed externally versus restricted to an internal network.

What should I do if I use Fleet?

Start by identifying all instances of Fleet within your environment and determining which teams own them. Verify whether these instances are accessible over the internet to understand your specific exposure. Once you have a clear inventory, prioritize these assets for remediation, such as updating to a version at or beyond 4.92.0.

References