Description
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.
Published: 2026-11-05
Score: 8.1 High
EPSS: n/a
KEV: No
Impact: Privilege Escalation and Unauthorized Data Access
Action: Immediate Patch
AI Analysis

Impact

An authorization bypass exists in the /credentials/signurl endpoint of Rucio. The API reads the X‑Rucio‑Account header instead of the account value supplied by the authenticated token, allowing any authenticated low‑privilege user to supply a header value of "root". This bypass satisfies the root‑only get_signed_url permission check and leads the server to generate a presigned URL for read, write or delete operations on arbitrary cloud storage objects. Due to the presence of an X‑Rucio‑VO header, an attacker may also select another tenant in multi‑VO deployments, enabling cross‑tenant data access.

Affected Systems

The vulnerability affects the Rucio framework from version 1.16.1 up to and including 35.9.0, 38.6.0, and 41.0.0rc1. All users of these releases are at risk if they have the ability to specify the X‑Rucio‑Account header in authenticated requests.

Risk and Exploitability

With a CVSS score of 8.1 this issue is high severity. The EPSS score is not available, and the vulnerability is not currently listed in the CISA KEV catalog. Exploitation requires only that the attacker be an authenticated user with low privilege, enabling straightforward subversion of authorization controls. Successful exploitation can lead to data disclosure, modification, deletion, and cross‑tenant access on cloud‑backed RSEs.

Generated by OpenCVE AI on November 5, 2026 at 23:21 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Rucio 35.9.0, 38.6.0, or 41.0.0rc1 or later to eliminate the bug.
  • Modify server configuration to reject or ignore the X‑Rucio‑Account header, ensuring the issuer value is always used.
  • Audit and enforce tenant boundaries so that the VO header matches the authenticated tenant, preventing cross‑tenant access.

Generated by OpenCVE AI on November 5, 2026 at 23:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-5j9r-fx4x-rpvg rucio has an Authorization Bypass on REST API endpoint for signing URLs
History

Fri, 06 Nov 2026 00:00:00 +0000

Type Values Removed Values Added
First Time appeared Rucio
Rucio rucio
Vendors & Products Rucio
Rucio rucio

Thu, 05 Nov 2026 22:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Rucio: Authorisation Bypass on REST API endpoint for signing URLs
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-05T21:56:20.677Z

Reserved: 2026-06-29T21:54:30.332Z

Link: CVE-2026-58273

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-05T22:18:49.230

Modified: 2026-11-05T22:18:49.230

Link: CVE-2026-58273

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-05T23:45:07Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key