Answer in brief
CVE-2026-100397 records a Critical severity (CVSS 10.0) vulnerability in Rucio: Improper Authentication via SSH Challenge Tokens. The current sources do not mark it as known exploited. The current feed maps rucio/rucio (generic), rucio (pip), rucio (pip), rucio (pip) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 10.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps rucio/rucio (generic), rucio (pip), rucio (pip), rucio (pip) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| rucio/ruciogeneric | >=1.14.0 <35.9.1 || >=36.0.0 <38.6.1 || >=39.0.0 <40.4.2 || >=41.0.0 <41.1.1 | 35.9.1, 38.6.1, 40.4.2, 41.1.1 |
| ruciopip | >=1.14.0.post1,<35.9.1 | 35.9.1 |
| ruciopip | >=36.0.0rc1,<38.6.1 | 38.6.1 |
| ruciopip | >=39.0.0rc1,<40.4.2 | 40.4.2 |
| ruciopip | >=41.0.0rc1,<41.1.1 | 41.1.1 |
| ruciopypi | >=1.14.0.post1 <35.9.1 | 35.9.1 |
| ruciopypi | >=36.0.0rc1 <38.6.1 | 38.6.1 |
| ruciopypi | >=39.0.0rc1 <40.4.2 | 40.4.2 |
| ruciopypi | >=41.0.0rc1 <41.1.1 | 41.1.1 |
Published upstream
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 13, 2026
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.
Quoted source text, attributed separately from HOL analysis.