PRIMARY-SOURCE REVIEW · 2026-11-13T18:25:00+09:00
Rucio: SSH challenges accepted as authentication tokens enable administrator impersonation
SSH challenges are nonces for a later key exchange, but are stored alongside authentication tokens and not distinguished during validation. An unauthenticated caller can request a challenge for an arbitrary account and use it within its short lifetime to access APIs as that account, including an administrator. Exact affected and fixed branches are retained below.
What to check
Update rucio to a fixed release on its branch: 35.9.1 / 38.6.1 / 40.4.2 / 41.1.1 or later. Review API exposure, authentication and privileged operations. Keep nonces separate from authenticated credentials.
A first fixed version is listed only when the advisory provides one. Advisory counts are not incident counts.
Affected and fixed versions by advisory (1)
GHSA-x585-4vv8-2mh2
Rucio: Unauthenticated administrator impersonation through SSH challenge tokens
rucio(pip): affected>= 1.14.0.post1, < 35.9.1→ fixed35.9.1rucio(pip): affected>= 36.0.0rc1, < 38.6.1→ fixed38.6.1rucio(pip): affected>= 39.0.0rc1, < 40.4.2→ fixed40.4.2rucio(pip): affected>= 41.0.0rc1, < 41.1.1→ fixed41.1.1
Primary sources
GitHub reviewed advisory API — saved publication window / Rucio maintainer advisory
Related topics
Active Storage: attachment alone can reach arbitrary file operations · Aspire: an unauthenticated NotFound route is not fixed by a runtime update · Hono: mount and router path differences can bypass authentication middleware · pgEdge RAG: ordinary concurrent queries can mix results across tenants · ScreenConnect: separate technician-client protection from compromise remediation · Air Terminal 6: OS command injection requires management login · KUSANAGI: the 11/12 revision clarifies Nginx redirect scope