<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 05:39:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-29080 — Rucio SQL Injection in FilterEngine Oracle JSON Path via DID Search API</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-29080</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rucio&lt;/p&gt;
&lt;p&gt;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/&amp;lt;scope&amp;gt;/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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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 MySQ…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rucio&lt;/p&gt;
&lt;p&gt;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/&amp;lt;scope&amp;gt;/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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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 MySQ…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-29080</guid>
    </item>
    <item>
      <title>GHSA-vjr5-c9qv-hgm3 — Rucio has SQL Injection in FilterEngine Oracle JSON Path via DID Search API</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vjr5-c9qv-hgm3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: rucio&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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/&amp;lt;scope&amp;gt;/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.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;**filter_engine.py:552** (string equality — default branch):
```python
expression = text(&amp;#34;json_exists({},&amp;#39;$?(@.{} {} \&amp;#34;{}\&amp;#34;)&amp;#39;)&amp;#34;.format(
    json_column.key, key, ORACLE_OP_MAP[oper], value))
```&lt;/p&gt;
&lt;p&gt;**filter_engine.py:548** (boolean branch):
```python
expression = text(&amp;#34;json_exists({},&amp;#39;$?(@.{}.boolean() {} \&amp;#34;{}\&amp;#34;)&amp;#39;)&amp;#34;.format(
    json_column.key, key, ORACLE_OP_MAP[oper], value))
```&lt;/p&gt;
&lt;p&gt;**filter_engine.py:550** (numeric branch — value unquoted):
```python
expression = text(&amp;#34;json_exists({},&amp;#39;$?(@.{} {} {})&amp;#39;)&amp;#34;.format(
    json_column.key…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: rucio&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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/&amp;lt;scope&amp;gt;/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.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;**filter_engine.py:552** (string equality — default branch):
```python
expression = text(&amp;#34;json_exists({},&amp;#39;$?(@.{} {} \&amp;#34;{}\&amp;#34;)&amp;#39;)&amp;#34;.format(
    json_column.key, key, ORACLE_OP_MAP[oper], value))
```&lt;/p&gt;
&lt;p&gt;**filter_engine.py:548** (boolean branch):
```python
expression = text(&amp;#34;json_exists({},&amp;#39;$?(@.{}.boolean() {} \&amp;#34;{}\&amp;#34;)&amp;#39;)&amp;#34;.format(
    json_column.key, key, ORACLE_OP_MAP[oper], value))
```&lt;/p&gt;
&lt;p&gt;**filter_engine.py:550** (numeric branch — value unquoted):
```python
expression = text(&amp;#34;json_exists({},&amp;#39;$?(@.{} {} {})&amp;#39;)&amp;#34;.format(
    json_column.key…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vjr5-c9qv-hgm3</guid>
    </item>
  </channel>
</rss>
