CVE-2026-100397 PUBLISHED

Rucio: Improper Authentication via SSH Challenge Tokens

Assigner: GitHub_M
Reserved: 25.09.2026 Published: 17.11.2026 Updated: 17.11.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS Score: 10

Product Status

Vendor rucio
Product rucio
Versions
  • Version >= 1.14.0, < 35.9.1 is affected
  • Version >= 36.0.0, < 38.6.1 is affected
  • Version >= 39.0.0, < 40.4.2 is affected
  • Version >= 41.0.0, < 41.1.1 is affected

References

Problem Types

  • CWE-287: Improper Authentication CWE