Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.4
CVE-2026-29080: Rucio Oracle Database Exposed to Unauthorized Access
GHSA-vjr5-c9qv-hgm3
CVE-2026-29080
Summary
Rucio users with Oracle databases may be at risk of unauthorized access to their data. An attacker can exploit this vulnerability to extract sensitive information such as passwords, authentication tokens, and data identifiers. Rucio users with Oracle databases should update their configuration to mitigate this risk.
What to do
- Update rucio to version 35.8.5.
- Update rucio to version 38.5.5.
- Update rucio to version 39.4.2.
- Update rucio to version 40.1.1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| pip | – | rucio |
>= 1.27.0, < 35.8.5 >= 36.0.0, < 38.5.5 >= 39.0.0, < 39.4.2 >= 40.0.0, < 40.1.1 Fix: upgrade to 35.8.5
|
| – | cern | rucio |
>= 1.27.0, < 35.8.5 >= 36.0.0, < 38.5.5 >= 39.0.0, < 39.4.2 >= 40.0.0, < 40.1.1 cpe:2.3:a:cern:rucio:*:*:*:*:*:*:*:* |
Original title
Rucio has SQL Injection in FilterEngine Oracle JSON Path via DID Search API
Original description
### Summary
A SQL injection vulnerability in the Oracle path of `FilterEngine.create_sqla_query` allows any authenticated Rucio user to execute arbitrary SQL against the backend database through the DID search endpoint (`GET /dids/<scope>/dids/search`). Attacker-controlled filter keys and values are interpolated directly into `sqlalchemy.text` via Python `str.format`, completely bypassing parameterization. This enables full database compromise including extraction of authentication tokens, password hashes, and all managed data identifiers. The vulnerability is affecting deployments using the default metadata plugin configuration `json_meta` with Oracle database backends.
### Details
*Will follow in two weeks (2025-05-19).*
### Impact
**Vulnerability type:** SQL Injection (CWE-89)
**Who is impacted:**
- **All Oracle-based Rucio deployments** using the default metadata plugin configuration (`json_meta`).
- ***Not affected*** are PostgreSQL/MySQL deployments using the default `json_meta` plugin (SQLAlchemy parameterizes the JSON path operations via bind parameters on non-Oracle dialects).
**What an attacker can do:**
- **Full database read access:** Extract any table including `identities` (password hashes and salts), `tokens` (active authentication sessions), `accounts` (user enumeration), `rse_settings` (storage endpoint credentials), and `rules` (data management policies).
- **Password hash extraction:** Combined with Rucio's use of single-iteration SHA-256 for password hashing (no KDF), extracted hashes can be cracked at GPU speed.
- **Authentication token theft:** Active bearer tokens can be extracted and used for immediate session hijacking.
- **Data modification:** Oracle PL/SQL enables `INSERT`/`UPDATE`/`DELETE` operations via DML within subqueries and PL/SQL blocks.
- **Potential remote code execution:** Via Oracle's `UTL_HTTP`, `DBMS_SCHEDULER`, or Java stored procedures if the database user has elevated privileges.
**Required attacker privileges:** Any authenticated Rucio user. Authentication tokens can be obtained via any supported method (userpass, x509, OIDC, SAML, SSH, GSS). No special roles or administrative permissions are required. The `GET /dids/<scope>/dids/search` endpoint is available to all authenticated users.
A SQL injection vulnerability in the Oracle path of `FilterEngine.create_sqla_query` allows any authenticated Rucio user to execute arbitrary SQL against the backend database through the DID search endpoint (`GET /dids/<scope>/dids/search`). Attacker-controlled filter keys and values are interpolated directly into `sqlalchemy.text` via Python `str.format`, completely bypassing parameterization. This enables full database compromise including extraction of authentication tokens, password hashes, and all managed data identifiers. The vulnerability is affecting deployments using the default metadata plugin configuration `json_meta` with Oracle database backends.
### Details
*Will follow in two weeks (2025-05-19).*
### Impact
**Vulnerability type:** SQL Injection (CWE-89)
**Who is impacted:**
- **All Oracle-based Rucio deployments** using the default metadata plugin configuration (`json_meta`).
- ***Not affected*** are PostgreSQL/MySQL deployments using the default `json_meta` plugin (SQLAlchemy parameterizes the JSON path operations via bind parameters on non-Oracle dialects).
**What an attacker can do:**
- **Full database read access:** Extract any table including `identities` (password hashes and salts), `tokens` (active authentication sessions), `accounts` (user enumeration), `rse_settings` (storage endpoint credentials), and `rules` (data management policies).
- **Password hash extraction:** Combined with Rucio's use of single-iteration SHA-256 for password hashing (no KDF), extracted hashes can be cracked at GPU speed.
- **Authentication token theft:** Active bearer tokens can be extracted and used for immediate session hijacking.
- **Data modification:** Oracle PL/SQL enables `INSERT`/`UPDATE`/`DELETE` operations via DML within subqueries and PL/SQL blocks.
- **Potential remote code execution:** Via Oracle's `UTL_HTTP`, `DBMS_SCHEDULER`, or Java stored procedures if the database user has elevated privileges.
**Required attacker privileges:** Any authenticated Rucio user. Authentication tokens can be obtained via any supported method (userpass, x509, OIDC, SAML, SSH, GSS). No special roles or administrative permissions are required. The `GET /dids/<scope>/dids/search` endpoint is available to all authenticated users.
ghsa CVSS3.1
9.9
ghsa CVSS4.0
9.4
Vulnerability type
CWE-89
SQL Injection
Published: 6 May 2026 · Updated: 1 Jun 2026 · First seen: 6 May 2026