Rucio up to 35.8.4/38.5.4/39.4.1/40.1.0 PostgreSQL Feature FilterEngine.create_postgres_query sql injection

Summaryinfo

A vulnerability classified as critical has been found in Rucio up to 35.8.4/38.5.4/39.4.1/40.1.0. The impacted element is the function FilterEngine.create_postgres_query of the component PostgreSQL Feature. The manipulation leads to sql injection. This vulnerability is uniquely identified as CVE-2026-29090. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Rucio up to 35.8.4/38.5.4/39.4.1/40.1.0. This issue affects the function FilterEngine.create_postgres_query of the component PostgreSQL Feature. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

### Summary A SQL injection vulnerability exists in Rucio versions 1.30.0 and later before 35.8.5, 38.5.5, 39.4.2, and 40.1.1, in `FilterEngine.create_postgres_query()`. This allows any authenticated Rucio user to execute arbitrary SQL against the PostgreSQL metadata database through the DID search endpoint (`GET /dids//dids/search`). When the `postgres_meta` metadata plugin is configured, attacker-controlled filter keys and values are interpolated directly into raw SQL strings via Python `.format()`, then passed to `psycopg3`'s `sql.SQL()` which treats the string as trusted SQL syntax. Depending on the database privileges assigned to the service account, exploitation can expose sensitive tables, modify or delete metadata, access server-side files, or achieve code execution through PostgreSQL features such as COPY ... FROM PROGRAM. This issue affects deployments that explicitly use the postgres_meta metadata plugin. This vulnerability has been fixed in versions 35.8.5, 38.5.5, 39.4.2, and 40.1.1.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-29090 since 03/03/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 35.8.5, 38.5.5, 39.4.2 or 40.1.1 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• Rucio

Version

• 35.8.0
• 35.8.1
• 35.8.2
• 35.8.3
• 35.8.4
• 38.5.0
• 38.5.1
• 38.5.2
• 38.5.3
• 38.5.4
• 39.4.0
• 39.4.1
• 40.0
• 40.1.0

Website

• Product: https://github.com/rucio/rucio/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion