The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-100397: Rucio flaw allows admin impersonation

By The Daily Byte ·14 Nov 2026 ·3 min read
Rows of server racks in the CERN data centre

A critical vulnerability in Rucio, the open-source framework used to manage large volumes of scientific data, lets an unauthenticated attacker impersonate any user, including an administrator, by abusing short-lived SSH challenge tokens. The flaw, tracked as CVE-2026-100397, was published on 13 November 2026 with a CVSS score of 9.8 out of 10.

The problem is that SSH challenge tokens are mistakenly accepted as valid credentials during authentication. A challenge token is meant to be a short-lived value used only as part of a subsequent SSH key exchange. But the function that validates authentication tokens does not distinguish challenge tokens from real authentication tokens.

Any account, no login needed

Because challenge tokens are generated from an account name supplied in a request header, without requiring any prior authentication, an attacker can request a valid challenge token for any account. The advisory shows the attack in two steps: request a token for the root account with a single header, then present that token as an authentication credential to other API endpoints.

The root cause is that challenge tokens are stored in the same database table as regular authentication tokens, and the validate_auth_token function in lib/rucio/core/authentication.py accepts them. The token works within a limited time window, but that is enough to call the API as the impersonated account and take whatever actions that account is allowed to perform.

What to do

The advisory was published alongside the CVE record on 13 November, and the day's security briefs list it among the day's critical vendor advisories. Teams running Rucio should treat the update as urgent even though no exploitation has been confirmed, because an authentication bypass of this kind is straightforward to attempt once the method is public.

Rucio has published a security advisory, GHSA-x585-4vv8-2mh2, and a patched release is listed there. Administrators should upgrade to the patched release named in the advisory and review access logs for unexpected authentication activity, particularly any use of SSH challenge tokens as bearer credentials.

Once inside with a stolen identity, an attacker acts with that account's permissions across the Rucio API, which manages accounts, data and storage for large research collaborations. That is why the ability to choose the victim account, including root, matters so much: the attacker does not need to escalate privileges afterwards, because the token already carries them.

The flaw is classified under CWE-287, improper authentication, and CWE-305, authentication bypass by primary weakness. No confirmed exploitation has been recorded and the flaw is not listed in CISA's Known Exploited Vulnerabilities catalogue, but the severity and the simplicity of the attack make it a priority fix for any organisation running Rucio. Sources: EchelonGraph and GitHub Security Advisory.