CVE 9 CRITICAL

Rucio SQL injection in postgres_meta DID search path compromises PostgreSQL metadata database_CVE-2026-29090

9 / 10
CRITICAL
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Description

### 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/<scope>/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.

AI Analysis

SQL injection vulnerability in Rucio's postgres_meta metadata plugin, allowing arbitrary SQL execution against the PostgreSQL metadata database.

Basic Information

ID CVE-2026-29090
Source GitHub_M
Published May 6, 2026 at 17:21
Modified May 6, 2026 at 18:17

Affected Product

Vendor rucio
Product rucio
Version >= 1.30.0, < 35.8.5
Affected Versions rucio rucio >= 1.30.0, < 35.8.5
rucio rucio >= 35.9.0, < 38.5.5
rucio rucio >= 38.6.0, < 39.4.2
rucio rucio >= 40.0.0, < 40.1.1

CWE Classification

AI Assessment

AI Score 9 / 10
AI Severity Critical
Vendor Rucio
Product Rucio
Version 1.30.0 to 35.8.4, 35.9.0 to 38.5.4, 38.6.0 to 39.4.1, 40.0.0 to 40.1.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.