CVE-2026-100397

Rucio: Improper Authentication via SSH Challenge Tokens

Published Nov 17, 2026 CVSS 3.1 · 10 Critical EPSS n/a KEV · Not listed
Description
Rucio is a scientific data management framework. From 1.14.0 until 35.9.1, 38.6.1, 40.4.2, and 41.1.1, validate_auth_token in lib/rucio/core/authentication.py does not distinguish short-lived SSH challenge nonces from authentication tokens stored in the same token table. An unauthenticated attacker can request /auth/ssh_challenge_token for an arbitrary account by supplying X-Rucio-Account, then present the returned X-Rucio-SSH-Challenge-Token as X-Rucio-Auth-Token to authenticate to other API endpoints as that account, including an administrative account. This issue is fixed in versions 35.9.1, 38.6.1, 40.4.2, and 41.1.1.

Analysis

AI-generated

Technical impact

Rucio permits unauthenticated clients to request an SSH challenge token for any account and then reuse that token as an authentication token. This flaw allows an attacker to impersonate any user, including privileged administrative accounts, with full control over the system. The weakness stems from the authentication routine not distinguishing between short‑lived challenge nonces and stored authentication tokens, a classic example of Improper Authentication (CWE‑287).

Affected Systems

The affected product is Rucio, a scientific data management framework. Versions from 1.14.0 up through 35.9.1, 38.6.1, 40.4.2, and 41.1.1 are vulnerable. Rucio releases 35.9.1, 38.6.1, 40.4.2, and 41.1.1 contain the patch that separates challenge tokens from authentication tokens.

Risk and Exploitability

The vulnerability has a CVSS score of 10, indicating critical severity. EPSS is not available, so the current exploitation likelihood cannot be quantified, but the absence of restrictions on the challenge token endpoint means an attacker could exploit it from any network position that can reach the Rucio API. The flaw is not listed in CISA’s KEV catalog, yet the open‑source nature of Rucio means that the exploit code could be freely distributed. Until a supported version is deployed, the risk persists.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Rucio to at least version 35.9.1, 38.6.1, 40.4.2, or 41.1.1 to apply the fix.
  • Disable the /auth/ssh_challenge_token endpoint or enforce strict rate limiting until the upgrade is completed.
  • Verify that any lingering SSH challenge tokens are cleared from the token table after the upgrade to prevent reuse.

Generated by OpenCVE AI on November 17, 2026 at 20:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-x585-4vv8-2mh2 Rucio: Unauthenticated administrator impersonation through SSH challenge tokens
History
Type Values Removed Values Added
First Time appeared Rucio
Rucio rucio
Vendors & Products Rucio
Rucio rucio
Type Values Removed Values Added
Description Rucio is a scientific data management framework. From 1.14.0 until 35.9.1, 38.6.1, 40.4.2, and 41.1.1, validate_auth_token in lib/rucio/core/authentication.py does not distinguish short-lived SSH challenge nonces from authentication tokens stored in the same token table. An unauthenticated attacker can request /auth/ssh_challenge_token for an arbitrary account by supplying X-Rucio-Account, then present the returned X-Rucio-SSH-Challenge-Token as X-Rucio-Auth-Token to authenticate to other API endpoints as that account, including an administrative account. This issue is fixed in versions 35.9.1, 38.6.1, 40.4.2, and 41.1.1.
Title Rucio: Improper Authentication via SSH Challenge Tokens
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 10, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 17, 2026, 7:35 PM
Reserved
Sep 25, 2026, 8:08 PM
Status
Received
Published
Nov 17, 2026, 8:17 PM
Modified
Nov 17, 2026, 8:17 PM