Rucio: Unauthenticated administrator impersonation through SSH challenge tokens
Summary
SSH challenge tokens are mistakenly accepted as valid credentials during the authentication token validation process.
While an SSH challenge token is intended as a short-lived nonce for use in a subsequent SSH key exchange, the function to validate authentication tokens does not differentiate between these and actual authentication tokens. Because challenge tokens are generated based on an account name provided via headers without requiring prior authentication, an unauthenticated attacker can request a valid "challenge" token for any account (including administrative ones) and use it to authenticate against other API endpoints.
Proof of Concept
The vulnerability exists because SSH challenge tokens are stored in the same database table as regular authentication tokens and validate_auth_token in lib/rucio/core/authentication.py accepts these "challenge" tokens. An attacker can obtain a challenge token for an account such as “root” via the REST API and then present it as a valid authentication bearer token:
- Request a challenge token for an arbitrary account (e.g., "root"):
curl -i -H "X-Rucio-Account: root" https://rucio/auth/ssh_challenge_token - The server returns a
200 OKwith the headerX-Rucio-SSH-Challenge-Token. - The attacker can then use this specific token within the ten-second challenge lifetime as an authentication credential in subsequent requests to the Rucio API:
curl -H "X-Rucio-Auth-Token: $CHALLENGE_TOKEN" https://rucio/accounts/whoami
What to do
Upgrade Rucio to version 35.9.1, 38.6.1, 40.4.2, 41.1.1, or later.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | rucio | >= 1.14.0.post1, < 35.9.1, >= 36.0.0rc1, < 38.6.1, >= 39.0.0rc1, < 40.4.2, >= 41.0.0rc1, < 41.1.1 | 35.9.1, 38.6.1, 40.4.2, 41.1.1 |
References
- https://github.com/rucio/rucio/security/advisories/GHSA-x585-4vv8-2mh2
- https://github.com/rucio/rucio/commit/f5db3546d9c0de4642dc9aa52e6a6e447911d680
- https://github.com/rucio/rucio/commit/e6525523e3bbe8ae34cbfc9b043ae52bda209b87
- https://github.com/rucio/rucio/commit/d7a3c2c2f933dce8edbcad07d8d076b9b782da35
- https://github.com/rucio/rucio/commit/b1725ee5477b683202174f0ec77ae00921bc3bd0
- https://github.com/rucio/rucio/commit/883d526c2f3c315cd775fb142038007053e3882b
- https://github.com/rucio/rucio/commit/8295d72a9e2d76abf9e98eb6f9a4ed5cb3bb1869
- https://github.com/rucio/rucio/commit/4df924feb539ef789b3e78cbc00712ef8cdf606e
- https://github.com/rucio/rucio/commit/4d4a58571ba853f3a55aef16ad9eb0944fce7483
- https://github.com/rucio/rucio/releases/tag/35.9.1
- https://github.com/rucio/rucio/releases/tag/35.9.1.post1
- https://github.com/rucio/rucio/releases/tag/38.6.1
- https://github.com/rucio/rucio/releases/tag/38.6.2
- https://github.com/rucio/rucio/releases/tag/40.4.2
- https://github.com/rucio/rucio/releases/tag/41.1.1
- https://github.com/rucio/rucio/releases/tag/41.2.0
- https://github.com/rucio/rucio
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-287, CWE-305- Platform
- Python (PyPI)
- Package
rucio- Disclosed
- 13.11.2026
- Updated
- 14.11.2026 10:00
Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.
OSV / GitHub Advisory Database - GHSA-x585-4vv8-2mh2 - CC BY 4.0
Vulnerability history: rucio
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 4
- First → latest
- 05.2026 11.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 3
- High 1
Disclosures per year
- 2026: 4
-
Rucio: Unauthenticated administrator impersonation through SSH challenge tokens this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.