CVE-2026-58273 json
Rucio: Authorisation Bypass on REST API endpoint for signing URLs
published 14d ago modified 5d ago also EUVD-2026-117819 , GHSA-5j9r-fx4x-rpvg
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi rucio 35.9.0, 38.6.0, 41.0.0rc1
- cern rucio 35.9.0, 38.6.0, 41.0.0rc1
Is CVE-2026-58273 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 5d ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/rucio/rucio/security/advisories/GHSA-5j9r-fx4x-rpvg referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | rucio | >=1.16.1, <35.9.0 >=36.0.0rc1, <38.6.0 >=39.0.0rc1, <41.0.0rc1 |
35.9.0 38.6.0 41.0.0rc1 |
Affected products
- rucio rucio
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/rucio/rucio/commit/64c0e6a6a93ae88427ff3b7d77532ce08c8a69ec
web
-
github.com
/rucio/rucio/commit/8bdc38994a8766658d0314d36afc104c9242c96f
web
-
github.com
/rucio/rucio/commit/8d9ba31514e6f5dca32b8c1db4738582cb37ec3a
web
-
github.com
/rucio/rucio/security/advisories/GHSA-5j9r-fx4x-rpvg
exploit, web
-
github.com
/rucio/rucio/releases/tag/35.9.0
web
-
github.com
/rucio/rucio/releases/tag/38.6.0
web
-
github.com
/rucio/rucio/releases/tag/41.0.0rc1
web
-
github.com
/rucio/rucio
package
Sources
- CVE List CVE-2026-58273
- GitHub Advisory GHSA-5j9r-fx4x-rpvg
- NVD CVE-2026-58273
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.