cve.bz

CVE-2026-100397 Rucio: Improper Authentication via SSH Challenge Tokens

10.0 criticalFix available

Critical (10.0) in rucio rucio. Fixed in rucio 35.9.1, 38.6.1, 40.4.2.

On this page
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.

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • rucio (PyPI): fixed in 35.9.1, 38.6.1, 40.4.2, 41.1.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-100397 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-100397?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-100397?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-100397 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
rucio>= 1.14.0, < 35.9.1
rucio>= 36.0.0, < 38.6.1
rucio>= 39.0.0, < 40.4.2
rucio>= 41.0.0, < 41.1.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-x585-4vv8-2mh2PyPIrucio>=1.14.0.post1 <35.9.135.9.1
GHSA-x585-4vv8-2mh2PyPIrucio>=36.0.0rc1 <38.6.138.6.1
GHSA-x585-4vv8-2mh2PyPIrucio>=39.0.0rc1 <40.4.240.4.2
GHSA-x585-4vv8-2mh2PyPIrucio>=41.0.0rc1 <41.1.141.1.1

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON