Security Digest · Vulnerability record

CVE-2026-100397: Rucio: Unauthenticated administrator impersonation through SSH challenge tokens

Rucio is a scientific data management framework.

CVSS 10.0 Critical EPSS 1.0% · p63

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 1.0%, percentile 63: FIRST’s model estimates a 1.0% chance of exploitation activity in the next 30 days, higher than 63% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes rucio (PyPI) >= 1.14.0.post1, < 35.9.1, fixed in 35.9.1; rucio (PyPI) >= 36.0.0rc1, < 38.6.1, fixed in 38.6.1; rucio (PyPI) >= 39.0.0rc1, < 40.4.2, fixed in 40.4.2; rucio (PyPI) >= 41.0.0rc1, < 41.1.1, fixed in 41.1.1. Check your lockfile, including transitive dependencies.

What it is

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, validateauthtoken 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/sshchallengetoken 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.

From the GitHub advisory

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 validateauthtoken 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:

Weakness type: CWE-287, CWE-305.

Product: rucio (PyPI) · Assigned by: GitHub_M · Published: 2026-11-17

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIrucio>= 1.14.0.post1, < 35.9.135.9.1
PyPIrucio>= 36.0.0rc1, < 38.6.138.6.1
PyPIrucio>= 39.0.0rc1, < 40.4.240.4.2
PyPIrucio>= 41.0.0rc1, < 41.1.141.1.1
VendorProductAffected versions (per CVE record)
ruciorucio>= 1.14.0, < 35.9.1, >= 36.0.0, < 38.6.1, >= 39.0.0, < 40.4.2, >= 41.0.0, < 41.1.1

Severity scores

Scored byCVSSScoreVector
GitHub_M3.110 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub3.19.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-11-21): 0.99% probability of exploitation activity in the next 30 days; percentile 63.

Timeline

  • — GitHub-reviewed advisory GHSA-x585-4vv8-2mh2 published (critical)
  • — CVE record published by GitHub_M
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-x585-4vv8-2mh2 github.com
  2. CVE.org record CVE-2026-100397 cve.org
  3. NVD entry CVE-2026-100397 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com
  5. github.com github.com
  6. github.com github.com
  7. github.com github.com
  8. github.com github.com
  9. github.com github.com
  10. github.com github.com
  11. github.com github.com
  12. github.com github.com
  13. github.com github.com
  14. github.com github.com
  15. github.com github.com
  16. github.com github.com

Critical PyPI advisories · Today’s Security Digest