CYBER CODE RED

Get real-time updates on Telegram

P4

CVE-2026-100397: rucio >= 1.14.0.post1, < 35.9.1, >= 36.0.0rc1, < 38.6.1, >= 39.0.0rc1, < 40.4.2 (+1 more affected versions)

CVE-2026-100397 affects rucio. CVSS 3.1 base score 9.8 (GitHub Advisory Database). Affected range: >= 1.14.0.post1, < 35.9.1. Fixed version: 35.9.1. Affected range: >= 36.0.0rc1, < 38.6.1. Fixed version: 38.6.1. Affected range: >= 39.0.0rc1, < 40.4.2. Fixed version: 40.4.2. Affected range: >= 41.0.0rc1, < 41.1.1. Fixed version: 41.1.1.

Affected technology

rucio · >= 1.14.0.post1, < 35.9.1
Vendor not specified by the source

rucio · >= 36.0.0rc1, < 38.6.1
Vendor not specified by the source

rucio · >= 39.0.0rc1, < 40.4.2
Vendor not specified by the source

rucio · >= 41.0.0rc1, < 41.1.1
Vendor not specified by the source

Description’s affected range: through SSH challenge tokens ## Summary SSH challenge tokens are mistakenly accepted as valid credentials during the authentication token validation process

Component: Not specified by the source

Attack conditions (GitHub Advisory Database, CVSS 3.1): Network (remote) · No privileges required · No user interaction required

What an attacker can do

The source says because challenge tokens are generated based on an account name provided via headers without requiring prior authentication, an unauthenticated attacker can request a valid "challenge" token for any account (including administrative ones) and use it to authenticate against other API endpoints. ## Proof of Concept The vulnerability exists because SSH challenge tokens are stored in the same database table as regular authentication tokens and `validate_auth_token` in `lib/rucio/core/authentication.py` accepts these "challenge" tokens. GitHub Advisory Database’s CVSS 3.1 assessment rates confidentiality, integrity and availability impact as high.

Published

Product
rucio
CCR priority
39.2 /100 (P4)
CVSS 3.1
9.8 /10 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H · GitHub Advisory Database
KEV
no

Provenance

Stable permalink: https://cybercodered.org/item/cve-cve-2026-100397.html