Rucio
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.14.0, < 35.9.1
- >= 36.0.0, < 38.6.1
- >= 39.0.0, < 40.4.2
- >= 41.0.0, < 41.1.1
Fixed in 35.9.1, 38.6.1, 40.4.2, 41.1.1
Mitigation
Upgrade rucio to 35.9.1 or 38.6.1 or 40.4.2 or 41.1.1 or later.
References
- Vendor advisory github.com/rucio/rucio/security/advisories/GHS…
- Patch github.com/rucio/rucio/commit/4d4a58571ba853f3…
- Patch github.com/rucio/rucio/commit/4df924feb539ef78…
5 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 pending
Pending 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| LLCForge/CVE-2026-100397 | 18 Nov 2026 +23 h | 18 Nov 2026 | 0 | Pending · listed by PoC Index; via PoC Index
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.