CVE
Rucio: Improper Authentication via SSH Challenge Tokens
Rucio 1.14.0 through 41.1.1 is affected when the SSH challenge token endpoint is reachable without prior authentication. Fixed in 35.9.1, 38.6.1, 40.4.2 and 41.1.1.
Written by a model from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 35.9.1, 38.6.1, 40.4.2, 41.1.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 35.9.1, 38.6.1, 40.4.2, 41.1.1.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Who should check
Teams running Rucio (pip package rucio) from 1.14.0 onward, including deployments whose API exposes the SSH challenge token endpoint.
“Affected versions >= 1.14.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 10.0
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 35.9.1, 38.6.1, 40.4.2, 41.1.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-100397 (Rucio: Improper Authentication via SSH Challenge Tokens), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-100397 (entry last updated 2026-11-17):
Affected:
- rucio rucio: from 1.14.0, fixed in 35.9.1; from 36.0.0, fixed in 38.6.1; from 39.0.0, fixed in 40.4.2; from 41.0.0, fixed in 41.1.1
Fixed versions: 35.9.1, 38.6.1, 40.4.2, 41.1.1.
Conditions (all must be true for the bug to be hit):
- The SSH challenge token endpoint (/auth/ssh_challenge_token) is reachable and accepts an X-Rucio-Account header without prior authentication. (source: https://github.com/rucio/rucio/security/advisories/GHSA-x585-4vv8-2mh2)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-100397 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-100397 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/rucio/rucio/security/advisories/GHSA-x585-4vv8-2mh2
- https://github.com/rucio/rucio/commit/4d4a58571ba853f3a55aef16ad9eb0944fce7483
- https://github.com/rucio/rucio/commit/4df924feb539ef789b3e78cbc00712ef8cdf606e
- https://github.com/rucio/rucio/commit/d7a3c2c2f933dce8edbcad07d8d076b9b782da35
- https://github.com/rucio/rucio/commit/f5db3546d9c0de4642dc9aa52e6a6e447911d680
- https://github.com/rucio/rucio/releases/tag/35.9.1
- https://github.com/rucio/rucio/releases/tag/38.6.1
- https://github.com/rucio/rucio/releases/tag/40.4.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-100397
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-100397"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- rucio rucio
From 1.14.0 · fixed in 35.9.1; From 36.0.0 · fixed in 38.6.1; From 39.0.0 · fixed in 40.4.2; From 41.0.0 · fixed in 41.1.1
Evidence 11
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 8
- Repository
- Repository
- Repository
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-100397
Is CVE-2026-100397 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The SSH challenge token endpoint generates tokens based on an account name supplied in the X-Rucio-Account header, and it does this without requiring prior authentication. This is an improper authentication flaw in how those challenge tokens are issued.Source: github.com
Which versions are affected by CVE-2026-100397?
rucio: from 1.14.0 before 35.9.1; from 36.0.0 before 38.6.1; from 39.0.0 before 40.4.2; from 41.0.0 before 41.1.1.Source: cve.now feed data
Am I affected, and how do I check?
Rucio versions 1.14.0 up to 35.9.1, 36.0.0 up to 38.6.1, 39.0.0 up to 40.4.2, and 41.0.0 up to 41.1.1 are in the affected ranges. The bug applies where the endpoint /auth/ssh_challenge_token is reachable and accepts an X-Rucio-Account header without prior authentication, so check the installed Rucio version and whether that endpoint can be reached without logging in.Source: github.com
How do I fix CVE-2026-100397?
Upgrade to the fixed version for your release line: 35.9.1, 38.6.1, 40.4.2, or 41.1.1. The facts do not list a separate workaround.Source: github.com