rucio · rucio · CWE-287 · published 2026-11-17

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

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-100397 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 1.1% chance of exploitation in the next 30 days, higher than 67% of all CVEs. This rucio vulnerability: CVSS 10.0 (v3.1), attacks can be automated, a successful attack gives total control of the component. Patch in your normal monthly cycle.

Share this

Remediation#

No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)1.1% (67th pct)FIRST EPSS v2026.06.15
CVSS base score10.0 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Weakness: CWE-287: Improper Authentication

Affected versions (from the CVE record)#

Description (from the CVE record)#

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 from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →