Threat Feed

CVE-2026-100397: rucio · Authentication bypass

Exploitation: Public exploit · CVSS 10.0 Critical · Unauthenticated · Published 2026-11-17

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.

Enclave's analysis

Rucio's token check can't tell short-lived SSH challenge nonces from real auth tokens. An unauthenticated attacker asks the challenge endpoint for a token for any account, such as root. They then send that token as the auth token and act as that account, admin included. The advisory has a two-request curl PoC. No in-the-wild exploitation is confirmed. Upgrade to 35.9.1, 38.6.1, 40.4.2 or 41.1.1.

Fix

Upgrade rucio (PyPI) to 35.9.1 or 38.6.1 or 40.4.2 or 41.1.1. No fixed version is listed for rucio; follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
rucio>= 1.14.0, < 35.9.1Not listed
rucio>= 36.0.0, < 38.6.1Not listed
rucio>= 39.0.0, < 40.4.2Not listed
rucio>= 41.0.0, < 41.1.1Not listed
rucio (PyPI)>= 1.14.0, < 35.9.135.9.1
rucio (PyPI)>= 36.0.0, < 38.6.138.6.1
rucio (PyPI)>= 39.0.0, < 40.4.240.4.2
rucio (PyPI)>= 41.0.0, < 41.1.141.1.1

Affected packages

  • pypi:rucio

Seen in 2 sources