External risk intelligence

Rucio Authentication Bypass Via SSH Challenge Token Impersonation

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-100397

Rucio is a data management framework that provides public-facing or organization-wide API endpoints for authentication and data operations. The vulnerability exists within the API authentication handling logic, which is commonly exposed to network traffic to facilitate remote access for users and services. Given its role as a network-accessible API service, it is likely to be reachable in environments where it is deployed.

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

A vulnerability in the Rucio data management framework could allow an unauthenticated attacker to impersonate any user, including administrators, by exploiting flaws in how authentication tokens are handled. This could lead to unauthorized access and control over scientific data repositories.

  • Allows unauthorized users to access any account.
  • Critical for protecting scientific research data integrity.
  • Assess Rucio usage for potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can impersonate any Rucio account, including administrative ones, by exploiting a flaw in how authentication tokens are handled. The attacker starts by requesting a challenge token for a target account and then uses this token to authenticate as that account to other API endpoints, potentially gaining unauthorized access and control.

  • No authentication is required to start.
  • The system incorrectly handles authentication tokens.
  • Can lead to unauthorized access and administrative control.

Live Threat

Current exploitation, exposure, and threat context

A critical vulnerability in Rucio's authentication mechanism could allow an unauthenticated attacker to impersonate any user, including administrators. This occurs because the system fails to distinguish between short-lived SSH challenge nonces and authentication tokens, enabling an attacker to reuse an SSH challenge to gain access to API endpoints.

  • User and administrative credentials.
  • Authentication tokens can be replayed.
  • Unauthorized access to sensitive data.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Rucio application owner or the platform team managing its deployment is likely responsible for addressing this vulnerability. The first practical step is to identify all Rucio instances, confirm their accessibility and business criticality, and then determine the accountable owner for remediation.

  • Identify all Rucio instances.
  • Verify exposure and criticality.
  • Plan remediation and vendor coordination.

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

Rucio is a scientific data management framework designed to handle large-scale data distribution, organization, and access. It is widely used in collaborative research environments to manage petabytes of data across distributed computing facilities. The software provides critical API endpoints that allow users and automated services to authenticate, track, and transfer data assets securely within a complex research infrastructure.

What is the vulnerability in CVE-2026-100397?

This vulnerability is an improper authentication flaw, categorized as CWE-287. It exists because the Rucio authentication system fails to properly distinguish between temporary security codes used for SSH challenges and permanent authentication tokens. Because both are stored in the same location, the software mistakenly accepts a short-lived challenge code as a valid, long-term session token, allowing for unauthorized account impersonation.

How does an attacker trigger this authentication bypass?

An attacker triggers the flaw by sending a specific request to the Rucio API's SSH challenge endpoint, providing the name of a target account. The system returns a challenge token which the attacker then submits to other sensitive API endpoints. Notably, this does not require any prior knowledge of the target's actual password or secret keys; the vulnerability exists simply because the system accepts the replayed challenge token as a valid authorization.

Is my Rucio deployment at risk according to Halo Surface Signal?

Halo Surface Signal indicates that because Rucio is a data management framework offering network-accessible API endpoints for authentication and data operations, it is likely to be reachable by external or internal network traffic. If your Rucio instance is configured to accept remote connections for distributed users or services, it is susceptible to this vulnerability since no prior authentication is needed to exploit it.

What should I do to secure my Rucio installation?

The first priority is to locate all active Rucio instances within your environment and document their business criticality. Once identified, verify which versions are currently running. If you are using a version affected by this flaw, you must upgrade to the patched release, such as 35.9.1, 38.6.1, 40.4.2, or 41.1.1, as recommended by the software vendor to correct the token handling logic and prevent unauthorized access.

References