CVE-2026-100397

Description

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.

Severity
CRITICAL
CVSS v3
10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H · source cna
Exploit chance (EPSS)
not scored
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2026-11-13GitHub advisory published (GHSA-x585-4vv8-2mh2)4 days before publication
  2. 2026-11-17Published by the CNA19:35 UTC

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-x585-4vv8-2mh2, affected packages:

EcosystemPackageVulnerable rangePatched
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

Affected products

VendorProduct
ruciorucio

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources