Auth bypass in Rucio

CVE-2026-58273

Rucio is a scientific data management framework. From 1.16.1 until 35.9.0, 38.6.0, and 41.0.0rc1, the /credentials/signurl endpoint reads X-Rucio-Account instead of the account stored in request.environ['issuer'] by token authentication. Any authenticated low-privilege user can supply root as the header value and pass the root-only get_signed_url permission check. The server then returns a presigned read, write, or delete URL for an attacker-selected object using stored S3, GCS, or Swift credentials, and X-Rucio-VO can select another tenant in multi-VO deployments. This permits data disclosure, modification, deletion, and cross-tenant access on cloud-backed RSEs. This issue is fixed in versions 35.9.0, 38.6.0, and 41.0.0rc1.

Vulnerability class: IDOR (Insecure Direct Object Reference)

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.

EPSS exploit prediction

No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.

Affected products

  • Rucio — versions >= 1.16.1, < 35.9.0, >= 36.0.0, < 38.6.0, >= 39.0.0, < 41.0.0rc1

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-58273?
CVE-2026-58273 is a high-severity vulnerability in Rucio, classified under Authorization Bypass Through User-Controlled Key. CVSS score: 8.1/10. Published 2026-11-05.
How severe is CVE-2026-58273?
High severity. CVSS v3 base score is 8.1 out of 10.