CVE-2026-100397

10.0Critical

Published 17 Nov 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.1-flash-lite

10.0CVSS

Critical

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
Full C/I/A compromise
Weakness
CWE-287

What an attacker gets

Unauthenticated attackers can gain full administrative access to any Rucio account. They only need to request a challenge token for a target account and reuse it as an authentication token.

Root cause

The authentication logic fails to differentiate between SSH challenge nonces and valid session tokens in the database.

Affected versions

Rucio 1.14.0 through 35.9.0, 38.0.0 through 38.6.0, 40.0.0 through 40.4.1, and 41.0.0 through 41.1.0.

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Fix & remediation

Upgrade to Rucio version 35.9.1, 38.6.1, 40.4.2, or 41.1.1. If you cannot patch immediately, disable the SSH authentication endpoint if it is not required for your operations.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-100397