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.
CVE-2026-58273
HIGHPre-NVD 8.18.8ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“▲” beside the score: it is higher than the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-28. A secondary CVSS source baseline 8.1; sources differ by 0.7.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-117819 (ENISA EUVD) · GHSA-5j9r-fx4x-rpvg (GitHub Security Advisories)Source: ENISA EUVD
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.8HIGHhigh confidence
- EG Risk
- 56EG Risk 56/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 46th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 28, 2026
Last Modified
November 12, 2026
Advisory Details (7)
Auto-updated Nov 5, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available
Rucio 41.0.0rc1 major release candidate
Patch available: rucio/rucio 41.0.0rc1 (pre-release)
https://github.com/rucio/rucio/releases/tag/41.0.0rc1GitHub release Patch Available
Rucio 38.6.0 LTS minor release
Patch available: rucio/rucio 38.6.0
https://github.com/rucio/rucio/releases/tag/38.6.0GitHub release Patch Available
Rucio 35.9.0 LTS minor release
Patch available: rucio/rucio 35.9.0
https://github.com/rucio/rucio/releases/tag/35.9.0GitHub commit Patch Available
commit 8d9ba31514e6 (rucio/rucio)
Patch available: rucio/rucio 38.6.0 (contains commit 8d9ba31514e6)
https://github.com/rucio/rucio/commit/8d9ba31514e6f5dca32b8c1db4738582cb37ec3aGitHub commit Patch Available
commit 8bdc38994a87 (rucio/rucio)
Patch available: rucio/rucio 35.9.0 (contains commit 8bdc38994a87)
https://github.com/rucio/rucio/commit/8bdc38994a8766658d0314d36afc104c9242c96fGitHub commit Patch Available
commit 64c0e6a6a93a (rucio/rucio)
Patch available: rucio/rucio 41.0.0rc1 (contains commit 64c0e6a6a93a)
https://github.com/rucio/rucio/commit/64c0e6a6a93ae88427ff3b7d77532ce08c8a69ecGitHub advisoryMentions a patch (unverified)🟡 PoC Available
Authorisation Bypass on REST API endpoint for signing URLs · Advisory · rucio/rucio · GitHub
https://github.com/rucio/rucio/security/advisories/GHSA-5j9r-fx4x-rpvgVendor Advisories for CVE-2026-58273(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | rucio @ 35.9.0 (fixes >= 1.16.1, < 35.9.0) | — | ghsa |
| pip | rucio @ 38.6.0 (fixes >= 36.0.0rc1, < 38.6.0) | — | ghsa |
| pip | rucio @ 41.0.0rc1 (fixes >= 39.0.0rc1, < 41.0.0rc1) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| rucio | 39.0.0 ... 40.4.2 (20 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 17× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 22:28 UTCEchelonGraph re-scored
- 2026-11-12 22:28 UTCGHSA enrichmentGHSA-5j9r-fx4x-rpvg · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-06 18:29 UTCEchelonGraph re-scored
- 2026-11-06 18:29 UTCGHSA enrichmentGHSA-5j9r-fx4x-rpvg · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-06 18:27 UTCEchelonGraph re-scored
- 2026-11-06 18:27 UTCGHSA enrichmentGHSA-5j9r-fx4x-rpvg · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-06 17:48 UTCEchelonGraph re-scored
- 2026-11-06 17:48 UTCGHSA enrichmentGHSA-5j9r-fx4x-rpvg · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-05 23:12 UTCENISA EUVD ID recordedEUVD-2026-117819 · Source: ENISA EUVD
- 2026-11-05 22:28 UTCEchelonGraph re-scored
- 2026-11-05 22:28 UTCGHSA enrichmentGHSA-5j9r-fx4x-rpvg · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-05 22:05 UTCEchelonGraph re-scored
- 2026-11-05 22:05 UTCGHSA enrichmentGHSA-5j9r-fx4x-rpvg · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-05 22:02 UTCMITRE cvelistV5CVSS v3 → 8.1
- 2026-11-04 19:08 UTCGHSA enrichmentGHSA-5j9r-fx4x-rpvg · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-01 07:42 UTCGHSA enrichmentGHSA-5j9r-fx4x-rpvg · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-01 07:42 UTCEchelonGraph re-scored
- 2026-10-28 20:42 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-58273?
CVE-2026-58273 is a high-severity vulnerability; its CVE record was published on October 28, 2026. 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…
When was the CVE record for CVE-2026-58273 published?
The CVE record for CVE-2026-58273 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-58273 actively exploited?
CVE-2026-58273 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58273?
CVE-2026-58273 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). EchelonGraph synthesises a secondary CVSS source + FIRST EPSS + GHSA into a combined EG score of 8.8 (HIGH).
How do I remediate CVE-2026-58273?
A fix for CVE-2026-58273 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58273 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58273
Is Your Infrastructure Affected by CVE-2026-58273?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.