PT-2026-146409

CVE-2026-100397

·

Published

2026-11-13

·

Updated

2026-11-13

Description by

CVSS 3.1
9.8
Critical
MetricsAV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Name of the Vulnerable Software and Affected Versions Rucio versions prior to 35.9.1 Rucio versions prior to 38.6.1
Description An issue exists where SSH challenge tokens are incorrectly accepted as valid credentials during the authentication token validation process. These tokens are intended as short-lived nonces for SSH key exchanges but are not differentiated from actual authentication tokens by the validate auth token() function in lib/rucio/core/authentication.py. Since challenge tokens are generated based on an account name provided in headers without requiring prior authentication, an unauthenticated attacker can request a challenge token for any account, including administrative ones, via the /auth/ssh challenge token endpoint. This token can then be used as a bearer token in the X-Rucio-Auth-Token header to authenticate against other API endpoints.
Recommendations Update to version 35.9.1 or later. Update to version 38.6.1 or later.
Exploitability
Fix
Impacts
Vendors
Affected products
Related identifiers
GHSA-X585-4VV8-2MH2
Found an issue in the description? Have something to add? Feel free to write us 👾