Advisory record · GHSA-6j7p-qjhg-9947

Rucio has SQL Injection in FilterEngine PostgreSQL Query Builder via DID Search API

CVSS 9.0 CriticalCriticalEPSS 0.0030 · 23rd percentile

Critical, because:

  • CVSS score 9.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
rucioPyPI>=1.30.0, <35.8.5 || >=36.0.0, <38.5.5 || >=39.0.0, <39.4.2 || >=40.0.0, <40.1.135.8.5, 38.5.5, 39.4.2, 40.1.1
Identifiers
GHSA-6j7p-qjhg-9947 · CVE-2026-29090 · PYSEC-2026-527
Weakness (CWE)
CWE-89
Published
29 Jun 2026
Updated
2 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Rucio package is vulnerable in versions 1.30.0 up to 35.8.5, 36.0.0 up to 38.5.5, 39.0.0 up to 39.4.2, and 40.0.0 up to 40.1.1. An authenticated Rucio user can send crafted filter input to the DID search endpoint when the postgres_meta metadata plugin is configured, injecting SQL into the PostgreSQL metadata database. The source describes possible data theft, data modification, and code execution on the database server, depending on database privileges. Upgrade to 35.8.5, 38.5.5, 39.4.2, or 40.1.1, depending on your release line.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.0 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0030, the 23rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 6 May 2026, 18:16 UTC Confirmed by NVD

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.