10.0
CRITICAL CVSS 3.1
CVE-2026-100397
Rucio: Improper Authentication via SSH Challenge Tokens
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.

INFO

Published Date :

Nov. 17, 2026, 8:17 p.m.

Last Modified :

Nov. 18, 2026, 5:17 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-100397 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 3.1 CRITICAL github
CVSS 3.1 CRITICAL MITRE-CVE
CVSS 3.1 CRITICAL [email protected]
Solution
Validate authentication tokens properly and distinguish them from SSH challenge tokens.
  • Distinguish SSH challenge tokens from authentication tokens.
  • Update the authentication token validation logic.
  • Ensure only valid authentication tokens are accepted.
  • Consider token lifecycle and scope.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-100397 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-100397 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-100397 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Nov. 18, 2026

    Action Type Old Value New Value
    Added Reference https://github.com/rucio/rucio/security/advisories/GHSA-x585-4vv8-2mh2
    Added SSVC {'id': 'CVE-2026-100397', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'poc'}, {'automatable': 'yes'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-11-18T16:43:41.101821Z'}
  • New CVE Received by [email protected]

    Nov. 17, 2026

    Action Type Old Value New Value
    Added 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.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
    Added CWE CWE-287
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/100xxx/CVE-2026-100397.json">CVE-2026-100397</a>
    Added Reference https://github.com/rucio/rucio/commit/4d4a58571ba853f3a55aef16ad9eb0944fce7483
    Added Reference https://github.com/rucio/rucio/commit/4df924feb539ef789b3e78cbc00712ef8cdf606e
    Added Reference https://github.com/rucio/rucio/commit/d7a3c2c2f933dce8edbcad07d8d076b9b782da35
    Added Reference https://github.com/rucio/rucio/commit/f5db3546d9c0de4642dc9aa52e6a6e447911d680
    Added Reference https://github.com/rucio/rucio/releases/tag/35.9.1
    Added Reference https://github.com/rucio/rucio/releases/tag/38.6.1
    Added Reference https://github.com/rucio/rucio/releases/tag/40.4.2
    Added Reference https://github.com/rucio/rucio/releases/tag/41.1.1
    Added Reference https://github.com/rucio/rucio/security/advisories/GHSA-x585-4vv8-2mh2
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.