rucio has an Authorization Bypass on REST API endpoint for signing URLs
影響: pip:rucio >= 1.16.1, < 35.9.0 → 35.9.0, pip:rucio >= 36.0.0rc1, < 38.6.0 → 38.6.0, pip:rucio >= 39.0.0rc1, < 41.0.0rc1 → 41.0.0rc1
The /credentials/signurl endpoint decides authorization from the client-supplied X-Rucio-Account HTTP header instead of the authenticated token's account. Any client holding any valid auth token (even a low-privilege account they legitimately own) can send X-Rucio-Account: root to pass the root-only permission check and have the Rucio server mint a presigned read / write / delete URL for an arbitrary object, signed with the RSE's stored S3 / GCS / Swift credentials. Details SignURL.get() takes…
Read on GitHub Advisory Database
| CVE | CVE-2026-58273 |
|---|---|
| Source | GitHub Advisory Database |
| Fetched | 10/29/2026, 09:48 AM |
| Data | Markdown JSON |
On 10/29/2026, 04:50 AM, GitHub Advisory Database published "rucio has an Authorization Bypass on REST API endpoint for signing URLs" (type: Advisory). Severity is "High" (high). Related technologies: Python, Swift. CVE: CVE-2026-58273.