Advisory

GHSA-x585-4vv8-2mh2

Also known as: CVE-2026-100397

Summary

Rucio: Unauthenticated administrator impersonation through SSH challenge tokens

Details

Summary

SSH challenge tokens are mistakenly accepted as valid credentials during the authentication token validation process.

While an SSH challenge token is intended as a short-lived nonce for use in a subsequent SSH key exchange, the function to validate authentication tokens does not differentiate between these and actual authentication tokens. 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. An attacker can obtain a challenge token for an account such as “root” via the REST API and then present it as a valid authentication bearer token:

  1. Request a challenge token for an arbitrary account (e.g., "root"): curl -i -H "X-Rucio-Account: root" https://rucio/auth/ssh_challenge_token
  2. The server returns a 200 OK with the header X-Rucio-SSH-Challenge-Token.
  3. The attacker can then use this specific token within the ten-second challenge lifetime as an authentication credential in subsequent requests to the Rucio API: curl -H "X-Rucio-Auth-Token: $CHALLENGE_TOKEN" https://rucio/accounts/whoami

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-11-13 01:09 UTC
Modified
2026-11-13 01:15 UTC

Affected packages and fixes

rucio

PyPI · All systems

Affected

  • introduced 1.14.0.post1, fixed 35.9.1 (ecosystem)

Fixed versions

35.9.1

Fix

  • Fixed version 35.9.1
    pip install --upgrade rucio==35.9.1

rucio

PyPI · All systems

Affected

  • introduced 36.0.0rc1, fixed 38.6.1 (ecosystem)

Fixed versions

38.6.1

Fix

  • Fixed version 38.6.1
    pip install --upgrade rucio==38.6.1

rucio

PyPI · All systems

Affected

  • introduced 39.0.0rc1, fixed 40.4.2 (ecosystem)

Fixed versions

40.4.2

Fix

  • Fixed version 40.4.2
    pip install --upgrade rucio==40.4.2

rucio

PyPI · All systems

Affected

  • introduced 41.0.0rc1, fixed 41.1.1 (ecosystem)

Fixed versions

41.1.1

Fix

  • Fixed version 41.1.1
    pip install --upgrade rucio==41.1.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences