CVE-2026-100397
Unauthenticated admin impersonation in Rucio via SSH challenge tokens
- CVSS 3.1
- 10.0 critical
- EPSS
- —
- Published
- ·
- Modified
Rucio treats short-lived SSH challenge tokens as valid authentication tokens. An unauthenticated remote attacker can request a challenge token for any account name, including administrative accounts, and present it as a bearer token to other API endpoints within the token's brief lifetime. That yields impersonation of the chosen account. Affected Rucio versions and fixed releases are not stated.
What to do: No fixed version is listed; apply the Rucio update for CVE-2026-100397 when it is available. No workaround is named.
| Product | Affected |
|---|---|
| Rucio | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
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.
- Ecosystems
- pip
- Weakness
- CWE-287
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- GHSA
- GHSA-x585-4vv8-2mh2 (critical)
In the news
0 storiesNo ingested article mentions this CVE yet.