Skip to content
Critical

CVE-2026-100397rucio Authentication Bypass

Rucio: Unauthenticated administrator impersonation through SSH challenge tokens

Published Nov 13, 2026 · Updated Nov 13, 2026 · Also known as GHSA-x585-4vv8-2mh2

Key Facts

Patch in the next maintenance window
  • CVE-2026-100397 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting rucio (pypi).
  • It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
  • Fixed versions are available, including rucio 35.9.1, rucio 38.6.1, rucio 40.4.2.
  • Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Scores

CVSS v3.1

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

n/a

Exploit maturity

None known

ATLAS score

28/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

None known

Public exploit code

0

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Advisories And Exploit References

Description

Summary

SSH challenge tokens are mistakenly accepted as valid credentials during the authentication token validation process.

While an SSH challenge token is intended as a short-lived nonce for use in a subsequent SSH key exchange, the function to validate authentication tokens does not differentiate between these and actual authentication tokens.

Because challenge tokens are generated based on an account name provided via headers without requiring prior authentication, an unauthenticated attacker can request a valid "challenge" token for any account (including administrative ones) and use it to authenticate against other API endpoints.

Proof of Concept

The vulnerability exists because SSH challenge tokens are stored in the same database table as regular authentication tokens and validate_auth_token in lib/rucio/core/authentication.py accepts these "challenge" tokens. An attacker can obtain a challenge token for an account such as “root” via the REST API and then present it as a valid authentication bearer token:

  1. Request a challenge token for an arbitrary account (e.g., "root"): curl -i -H "X-Rucio-Account: root" https://rucio/auth/ssh_challenge_token
  2. The server returns a 200 OK with the header X-Rucio-SSH-Challenge-Token.
  3. The attacker can then use this specific token within the ten-second challenge lifetime as an authentication credential in subsequent requests to the Rucio API: curl -H "X-Rucio-Auth-Token: $CHALLENGE_TOKEN" https://rucio/accounts/whoami

Affected Products

1 affected entries in total
ProductAffected versionsFixed in
ruciopypi>= 1.14.0.post135.9.1

Patched Releases

rucio

35.9.1, 38.6.1, 40.4.2, 41.1.1

Timeline

  1. Publicly disclosed

    Nov 13, 2026

Weakness Type

  • CWE-287 Improper Authentication
  • CWE-305 Authentication Bypass by Primary Weakness

References

13 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2026-100397 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Nov 17, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.