CVE-2026-29080
SQL Injection in Rucio via FilterEngine
Publication date: 2026-05-06
Last updated on: 2026-05-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rucio | rucio | From 1.27.0 (inc) to 35.8.5 (exc) |
| rucio | rucio | 35.8.5 |
| rucio | rucio | 38.5.5 |
| rucio | rucio | 39.4.2 |
| rucio | rucio | 40.1.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the Rucio software, specifically in the method FilterEngine.create_sqla_query(). It allows any authenticated user to execute arbitrary SQL commands on the backend Oracle database through the DID search endpoint.
The issue arises because attacker-controlled filter keys and values are directly inserted into a raw SQL fragment using Python string formatting without proper parameterization or escaping. This happens only on Oracle database deployments using the default json_meta plugin.
Exploiting this vulnerability can lead to full database compromise, including extraction of sensitive information such as authentication tokens, password hashes, and all managed data identifiers.
How can this vulnerability impact me? :
If exploited, this vulnerability can allow an authenticated user to execute arbitrary SQL commands on the backend Oracle database, leading to a full compromise of the database.
- Extraction of authentication tokens and password hashes.
- Access to all managed data identifiers.
- Exposure of sensitive tables such as identities, tokens, accounts, rse_settings, and rules.
- Potential modification or deletion of database contents.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Rucio to a fixed version. The vulnerability has been fixed in versions 35.8.5, 38.5.5, 39.4.2, and 40.1.1.
If upgrading immediately is not possible, restrict access to the DID search endpoint to trusted users only, and monitor for unusual database activity, especially on Oracle deployments using the default json_meta plugin.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability allows authenticated users to execute arbitrary SQL commands on the backend database, potentially exposing sensitive data such as authentication tokens, password hashes, and all managed data identifiers.
Such exposure and potential unauthorized access to sensitive personal and authentication data could lead to non-compliance with data protection regulations and standards like GDPR and HIPAA, which require strict controls over access to personal and sensitive information.
Therefore, exploitation of this vulnerability could result in violations of confidentiality, integrity, and availability requirements mandated by these regulations.