<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T10:01:30.582796+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-308775</id>
    <title>EUVD-2026-308775</title>
    <updated>2026-10-03T10:01:30.648206+00:00</updated>
    <content>EUVD-2026-308775</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-308775"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-29080</id>
    <title>fkie_cve-2026-29080</title>
    <updated>2026-10-03T10:01:30.648276+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>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/&lt;scope&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.</p>
<p>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.</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-29080"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vjr5-c9qv-hgm3</id>
    <title>GHSA-vjr5-c9qv-hgm3 — Rucio has SQL Injection in FilterEngine Oracle JSON Path via DID Search API</title>
    <updated>2026-10-03T10:01:30.648378+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: rucio</p>
<p>### Summary</p>
<p>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/&lt;scope&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.</p>
<p>---</p>
<p>### Details</p>
<p>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:</p>
<p>**filter_engine.py:552** (string equality — default branch):
```python
expression = text("json_exists({},'$?(@.{} {} \"{}\")')".format(
    json_column.key, key, ORACLE_OP_MAP[oper], value))
```</p>
<p>**filter_engine.py:548** (boolean branch):
```python
expression = text("json_exists({},'$?(@.{}.boolean() {} \"{}\")')".format(
    json_column.key, key, ORACLE_OP_MAP[oper], value))
```</p>
<p>**filter_engine.py:550** (numeric branch — value unquoted):
```python
expression = text("json_exists({},'$?(@.{} {} {})')".format(
    json_column.key…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vjr5-c9qv-hgm3"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-528</id>
    <title>PYSEC-2026-528 — Rucio has SQL Injection in FilterEngine Oracle JSON Path via DID Search API</title>
    <updated>2026-10-03T10:01:30.648585+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: rucio</p>
<p>### Summary</p>
<p>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/&lt;scope&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.</p>
<p>### Details</p>
<p>*Will follow in two weeks (2025-05-19).*</p>
<p>### Impact</p>
<p>**Vulnerability type:** SQL Injection (CWE-89)</p>
<p>**Who is impacted:**</p>
<p>- **All Oracle-based Rucio deployments** using the default metadata plugin configuration (`json_meta`).
- ***Not affected*** are PostgreSQL/MySQL deployments using the default `json_meta` plugin (SQLAlchemy parameterizes the JSON path operations via bind parameters on non-Oracle dialects).</p>
<p>**What an attacker can do:**</p>
<p>- **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), and `rules` (data management policies).
- **Password hash extraction:** Combined with Rucio's use of single-iteration SHA-256 for pass…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-528"/>
  </entry>
</feed>
