Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
10.0
CVE-2026-100397: Rucio lets attackers log in as any user
CVE-2026-100397 · published 4 days ago
Summary
The Rucio data management system fails to separate temporary SSH challenge tokens from regular login tokens. An unauthenticated person could request a challenge token for any account and then use it to gain access to that account, even with administrative privileges. Upgrade to the latest patched version of Rucio to close the gap.
What to do
- Update rucio rucio to version 35.9.1.
- Update rucio rucio to version 38.6.1.
- Update rucio rucio to version 40.4.2.
- Update rucio rucio to version 41.1.1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| pip | rucio | 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 Fix: upgrade to 35.9.1
|
| – | rucio | rucio | >= 1.14.0, < 35.9.1 |
Original advisory text
Rucio: Improper Authentication via SSH Challenge Tokens
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
- https://github.com/rucio/rucio/security/advisories/GHSA-x585-4vv8-2mh2 Vendor Advisory
- https://github.com/rucio/rucio/commit/4d4a58571ba853f3a55aef16ad9eb0944fce7483 Patch
- https://github.com/rucio/rucio/commit/4df924feb539ef789b3e78cbc00712ef8cdf606e Patch
- https://github.com/rucio/rucio/commit/8295d72a9e2d76abf9e98eb6f9a4ed5cb3bb1869
- https://github.com/rucio/rucio/commit/883d526c2f3c315cd775fb142038007053e3882b
- https://github.com/rucio/rucio/commit/b1725ee5477b683202174f0ec77ae00921bc3bd0
- https://github.com/rucio/rucio/commit/d7a3c2c2f933dce8edbcad07d8d076b9b782da35 Patch
- https://github.com/rucio/rucio/commit/e6525523e3bbe8ae34cbfc9b043ae52bda209b87
- https://github.com/rucio/rucio/commit/f5db3546d9c0de4642dc9aa52e6a6e447911d680 Patch
- https://github.com/rucio/rucio/releases/tag/35.9.1 URL
- https://github.com/rucio/rucio/releases/tag/35.9.1.post1
- https://github.com/rucio/rucio/releases/tag/38.6.2
- https://github.com/rucio/rucio/releases/tag/41.2.0
- https://github.com/advisories/GHSA-x585-4vv8-2mh2
- https://github.com/rucio/rucio/releases/tag/38.6.1 URL
- https://github.com/rucio/rucio/releases/tag/40.4.2 URL
- https://github.com/rucio/rucio/releases/tag/41.1.1 URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/100xxx/CVE-2026-1003... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-100397 Vendor Advisory
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Severity
10.0
Critical
Type
CWE-287Improper Authentication
CWE-305Authentication Bypass by Primary Weakness
Timeline
Published17 Nov 2026
Updated22 Nov 2026
First seen13 Nov 2026
Sources
GHSA-x585-4vv8-2mh2 · GHSA
CVE-2026-100397 · NVD
CVE-2026-100397 · MITRE
CVE-2026-100397 · OSV
Track software like this
Free during beta