VulnerabilityPublished 5 Nov 2026

CVE-2026-58273: rucio · Insecure Direct Object Reference

Affects rucioSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.1 High · fixed in 41.0.0rc1 : patch rucio soon.

Data as of 5 Nov 2026, 22:20 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	8.1

Patch: Available – fixed in 41.0.0rc1, 38.6.0, 35.9.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade rucio to 41.0.0rc1, 38.6.0 or 35.9.0.

Affected software

Product	Affected	Fixed in
ruciorucio	Affected >=39.0.0 <41.0.0rc1	Fixed in 41.0.0rc1
ruciorucio	Affected >=36.0.0 <38.6.0	Fixed in 38.6.0
ruciorucio	Affected >=1.16.1 <35.9.0	Fixed in 35.9.0

AI-suggested

A fix is available and has been released in Rucio versions 35.9.0, 38.6.0, and 41.0.0rc1. Users should upgrade to one of these fixed versions to remediate the vulnerability. Since this is a server-side issue in the open-source Rucio software, applying the official patch is the recommended mitigation. No vendor advisory indicates that no action is required or that the issue is already mitigated by other means.

Description

CVE-2026-58273 is an authorization bypass vulnerability in the Rucio scientific data management framework affecting versions from 1.16.1 up to but not including 35.9.0, 38.6.0, and 41.0.0rc1. The vulnerability arises because the /credentials/signurl endpoint improperly uses the X-Rucio-Account header supplied by the user instead of the authenticated account from the token, allowing low-privilege users to impersonate the root account. This enables unauthorized generation of presigned URLs for read, write, or delete operations on cloud-backed storage, potentially leading to data disclosure, modification, deletion, and cross-tenant access. The issue is fixed in versions 35.9.0, 38.6.0, and 41.0.0rc1.

Impact

An authenticated low-privilege user can bypass authorization controls to impersonate the root account when requesting presigned URLs. This leads to unauthorized access to cloud-backed storage objects, including the ability to read, modify, or delete data. Additionally, in multi-VO deployments, the attacker can access data across tenants, resulting in significant confidentiality and integrity violations. Availability impact is not indicated. The CVSS 3.1 score is 8.1 (High), reflecting network attack vector, low complexity, low privileges required, no user interaction, and high confidentiality and integrity impact.

Summary

Rucio versions >=1.16.1 and <35.9.0, >=36.0.0 and <38.6.0, and >=39.0.0 and <41.0.0rc1 contain an authorization bypass vulnerability (CWE-639) in the /credentials/signurl endpoint. The endpoint reads the X-Rucio-Account header provided by the user instead of the authenticated account from request.environ['issuer']. This flaw allows any authenticated user with low privileges to specify 'root' as the account header, bypassing root-only permission checks for get_signed_url. Consequently, an attacker can obtain presigned URLs for objects stored on S3, GCS, or Swift cloud storage, enabling unauthorized data disclosure, modification, deletion, and cross-tenant access in multi-VO deployments. The vulnerability is addressed in fixed versions 35.9.0, 38.6.0, and 41.0.0rc1.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 22:20 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats