cve.bz

CVE-2026-58273 rucio rucio

8.1 highEPSS 0.6%Fix available

High (8.1) in rucio rucio. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in rucio 35.9.0, 38.6.0, 41.0.0rc1.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • rucio (PyPI): fixed in 35.9.0, 38.6.0, 41.0.0rc1

Ask an AI about this CVE

Show the promptExplain CVE-2026-58273 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-58273?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-58273?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-58273 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
rucio>= 1.16.1, < 35.9.0
rucio>= 36.0.0, < 38.6.0
rucio>= 39.0.0, < 41.0.0rc1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5j9r-fx4x-rpvgPyPIrucio>=1.16.1 <35.9.035.9.0
GHSA-5j9r-fx4x-rpvgPyPIrucio>=36.0.0rc1 <38.6.038.6.0
GHSA-5j9r-fx4x-rpvgPyPIrucio>=39.0.0rc1 <41.0.0rc141.0.0rc1

References

Check your stackJSON