NVD published 17 Nov 2026
CVE-2026-100397
1 public exploit.
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.
Signals
- KEV, exploited in the wild
- no
- EPSS, 30-day forecast
- 1.1%, 67th percentile (as of 18 Nov 2026)
- CVSS, NVD, CRITICAL
- 10.0
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Internet exposure
- not stated
Not in CISA's catalogue as of the last daily pull. Absence is not proof of safety.
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 1 dispatch
Public exploit code 1 known · links only
GitHub PoCs 1Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars1
- LLCForge/CVE-2026-1003970 stars
Caution 75 · 1 flag
- new owner account (new_owner_account)
CVE-2026-100397 — Rucio SSH challenge token auth bypass (CVSS 10.0). Unauthenticated account impersonation via forged SSH challenge tokens.
created 18 Nov 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.