CVE-2026-100397
Rucio is a scientific data management framework. From 1.14.0 until …
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/rucio/rucio/security/advisories/GHSA-x585-4vv8-2mh2
- github.com/rucio/rucio/commit/4d4a58571ba853f3a55aef16ad9eb0944fce7483
- github.com/rucio/rucio/commit/4df924feb539ef789b3e78cbc00712ef8cdf606e
- github.com/rucio/rucio/commit/8295d72a9e2d76abf9e98eb6f9a4ed5cb3bb1869
- github.com/rucio/rucio/commit/883d526c2f3c315cd775fb142038007053e3882b
- github.com/rucio/rucio/commit/b1725ee5477b683202174f0ec77ae00921bc3bd0
- github.com/rucio/rucio/commit/d7a3c2c2f933dce8edbcad07d8d076b9b782da35
- github.com/rucio/rucio/commit/e6525523e3bbe8ae34cbfc9b043ae52bda209b87
- nvd.nist.gov/vuln/detail/CVE-2026-100397
- cve.org/CVERecord?id=CVE-2026-100397
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.