SQL Injection in rucio (CVE-2026-29080)
Summary
SQL injection in rucio (CVE-2026-29080). Successful exploitation can lead to full system takeover. Exploitable via GET /dids/. Mitigation: upgrade to 40.1.1 or later.
Original description
The description as published by the source.
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//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_metaplugin (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), andrules(data management policies). - Password hash extraction: Combined with Rucio's use of single-iteration SHA-256 for password has…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-29080 has been found in rucio.
Attackers can target a specific entry point like GET /dids/ over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade rucio to 40.1.1 or later.
If unsure, ask your IT team or search "rucio CVE-2026-29080" on the vendor's site.
CVE-2026-29080 (rucio) — CWE-89 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /dids/ / FilterEngine.create_sqla_query / sqlalchemy.text / str.format
Patched: 40.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in rucio. Attackers reach the vulnerable code path via GET /dids/.
Check the vendor advisory for the affected versions of rucio. Attack surface: GET /dids/ / FilterEngine.create_sqla_query / sqlalchemy.text / str.format.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 40.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /dids/ requests with malformed payloads or SQL meta-characters. Run grep -r 'rucio' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'rucio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
rucioを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /dids/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /dids/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade rucio to 40.1.1ステージング環境で 40.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /dids/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com