CVE-2026-29080
Rucio SQL Injection in FilterEngine Oracle JSON Path via DID Search API
Description
A SQL injection vulnerability in `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`). On Oracle deployments attacker-controlled filter keys and values are interpolated directly into `sqlalchemy.text()` via Python `.format()`, completely bypassing parameterization. This enables full database compromise including extraction of authentication tokens, password hashes, and all managed data identifiers. This affects versions 1.27.0 and later before 35.8.5, 38.5.5, 39.4.2, and 40.1.1. The vulnerability exists in `lib/rucio/core/did_meta_plugins/filter_engine.py` within the `create_sqla_query()` method. When the database dialect is Oracle, filter expressions for JSON metadata columns are constructed using `text()` with Python string formatting. Both `key` and `value` are attacker-controlled strings derived from HTTP query parameters. The `text()` function creates a raw SQL fragment — it does **not** escape or parameterize its contents. Any authenticated Rucio user can exploit this through the DID search API to execute arbitrary SQL against the backend database. This can expose all managed data identifiers and sensitive tables such as identities, tokens, accounts, rse_settings, and rules, and may allow modification of database contents. The issue affects Oracle deployments using the default json_meta plugin and does not affect PostgreSQL or MySQL deployments using that plugin. This vulnerability has been fixed in versions 35.8.5, 38.5.5, 39.4.2, and 40.1.1.
INFO
Published Date :
May 6, 2026, 5:16 p.m.
Last Modified :
Nov. 11, 2026, 11:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | HIGH | [email protected] | ||||
| CVSS 4.0 | CRITICAL | [email protected] |
Solution
- Update Rucio to version 35.8.5 or later.
- Update Rucio to version 38.5.5 or later.
- Update Rucio to version 39.4.2 or later.
- Update Rucio to version 40.1.1 or later.
Public PoC/Exploit Available at Github
CVE-2026-29080 has a 1 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-29080.
| URL | Resource |
|---|---|
| https://github.com/rucio/rucio/security/advisories/GHSA-vjr5-c9qv-hgm3 | Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-29080 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-29080
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Archived EGI SVG Advisories
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-29080 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-29080 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Nov. 11, 2026
Action Type Old Value New Value Added Translation Title: Rucio, Description: Una vulnerabilidad de inyección SQL en ’FilterEngine.create_sqla_query()’ permite a cualquier usuario Rucio autenticado ejecutar SQL arbitrario contra la base de datos backend a través del endpoint de búsqueda de DID (’GET /dids/[scope]/dids/search’). En despliegues de Oracle, las claves y valores de filtro controlados por el atacante se interpolan directamente en ’sqlalchemy.text()’ a través de Python ’.format()’, omitiendo completamente la parametrización. Esto permite el compromiso total de la base de datos, incluyendo la extracción de tokens de autenticación, hashes de contraseñas y todos los identificadores de datos gestionados. Esto afecta a las versiones 1.27.0 y posteriores anteriores a 35.8.5, 38.5.5, 39.4.2 y 40.1.1. La vulnerabilidad existe en ’lib/rucio/core/did_meta_plugins/filter_engine.py’ dentro del método ’create_sqla_query()’. Cuando el dialecto de la base de datos es Oracle, las expresiones de filtro para columnas de metadatos JSON se construyen usando ’text()’ con formato de cadena de Python. Tanto ’key’ como ’value’ son cadenas controladas por el atacante derivadas de parámetros de consulta HTTP. La función ’text()’ crea un fragmento SQL en bruto - no escapa ni parametriza su contenido. Cualquier usuario Rucio autenticado puede explotar esto a través de la API de búsqueda de DID para ejecutar SQL arbitrario contra la base de datos backend. Esto puede exponer todos los identificadores de datos gestionados y tablas sensibles como identidades, tokens, cuentas, rse_settings y reglas, y puede permitir la modificación del contenido de la base de datos. El problema afecta a los despliegues de Oracle que utilizan el plugin json_meta predeterminado y no afecta a los despliegues de PostgreSQL o MySQL que utilizan ese plugin. Esta vulnerabilidad ha sido corregida en las versiones 35.8.5, 38.5.5, 39.4.2 y 40.1.1. -
CVE Modified by [email protected]
Jun. 17, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'rucio', 'product': 'rucio', 'versions': [{'status': 'affected', 'version': '>= 1.27.0, < 35.8.5'}, {'status': 'affected', 'version': '>= 35.9.0, < 38.5.5'}, {'status': 'affected', 'version': '>= 38.6.0, < 39.4.2'}, {'status': 'affected', 'version': '>= 40.0.0, < 40.1.1'}]}] -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jun. 17, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-29080', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-05-06T17:21:09.695320Z'} -
Initial Analysis by [email protected]
May. 11, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Added CPE Configuration OR *cpe:2.3:a:cern:rucio:*:*:*:*:*:*:*:* versions from (including) 36.0.0 up to (excluding) 38.5.5 *cpe:2.3:a:cern:rucio:*:*:*:*:*:*:*:* versions from (including) 39.0.0 up to (excluding) 39.4.2 *cpe:2.3:a:cern:rucio:*:*:*:*:*:*:*:* versions from (including) 40.0.0 up to (excluding) 40.1.1 *cpe:2.3:a:cern:rucio:*:*:*:*:*:*:*:* versions from (including) 1.27.0 up to (excluding) 35.8.5 Added Reference Type GitHub, Inc.: https://github.com/rucio/rucio/security/advisories/GHSA-vjr5-c9qv-hgm3 Types: Vendor Advisory -
New CVE Received by [email protected]
May. 06, 2026
Action Type Old Value New Value Added Description A SQL injection vulnerability in `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`). On Oracle deployments attacker-controlled filter keys and values are interpolated directly into `sqlalchemy.text()` via Python `.format()`, completely bypassing parameterization. This enables full database compromise including extraction of authentication tokens, password hashes, and all managed data identifiers. This affects versions 1.27.0 and later before 35.8.5, 38.5.5, 39.4.2, and 40.1.1. The vulnerability exists in `lib/rucio/core/did_meta_plugins/filter_engine.py` within the `create_sqla_query()` method. When the database dialect is Oracle, filter expressions for JSON metadata columns are constructed using `text()` with Python string formatting. Both `key` and `value` are attacker-controlled strings derived from HTTP query parameters. The `text()` function creates a raw SQL fragment — it does **not** escape or parameterize its contents. Any authenticated Rucio user can exploit this through the DID search API to execute arbitrary SQL against the backend database. This can expose all managed data identifiers and sensitive tables such as identities, tokens, accounts, rse_settings, and rules, and may allow modification of database contents. The issue affects Oracle deployments using the default json_meta plugin and does not affect PostgreSQL or MySQL deployments using that plugin. This vulnerability has been fixed in versions 35.8.5, 38.5.5, 39.4.2, and 40.1.1. Added CVSS V4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Added CWE CWE-89 Added Reference https://github.com/rucio/rucio/security/advisories/GHSA-vjr5-c9qv-hgm3