CVE-2026-29080

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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//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.

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.

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 MySQL deployments using that plugin.

This vulnerability has been fixed in versions 35.8.5, 38.5.5, 39.4.2, and 40.1.1.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

Published

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (1)

Auto-updated May 6, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

SQL Injection in FilterEngine Oracle JSON Path via DID Search API · Advisory · rucio/rucio · GitHub

https://github.com/rucio/rucio/security/advisories/GHSA-vjr5-c9qv-hgm3

Vendor Advisories for CVE-2026-29080(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
rucio1.27.0 ... 40.1.0 (182 versions)
  • 1.27.0 up to 35.8.5: fixed in 35.8.5
  • 36.0.0 up to 38.5.5: fixed in 38.5.5
  • 39.0.0 up to 39.4.2: fixed in 39.4.2
  • 40.0.0 up to 40.1.1: fixed in 40.1.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-30 09:11 UTCOSV refresh
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 00:26 UTCEPSS rescore
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-20 20:15 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 19:27 UTCEPSS rescore
  19. 2026-09-17 19:30 UTCEPSS rescore
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-12 15:01 UTCEPSS rescore
  24. 2026-09-11 15:40 UTCOSV refresh
  25. 2026-09-11 14:52 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 09:34 UTCEPSS rescore
  2. 2026-09-08 22:00 UTCEPSS rescore
  3. 2026-09-07 16:01 UTCEPSS rescore
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:11 UTCEPSS rescore
  8. 2026-09-01 13:53 UTCEPSS rescore
  9. 2026-09-01 04:39 UTCEPSS rescore
  10. 2026-09-01 04:39 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-24 14:17 UTCEPSS rescore
  17. 2026-08-23 19:47 UTCEG score recompute
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 12:53 UTCEG score recompute
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 04:51 UTCEG score recompute
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 03:24 UTCEG score recompute
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-12 16:59 UTCEG score recompute
  33. 2026-08-12 13:50 UTCEPSS rescore
  34. 2026-08-11 15:59 UTCEG score recompute
  35. 2026-08-11 13:42 UTCEPSS rescore
  36. 2026-08-11 01:30 UTCEG score recompute
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 14:35 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 02:33 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-08 01:56 UTCEG score recompute
  43. 2026-08-07 01:53 UTCEG score recompute
  44. 2026-08-06 13:46 UTCEPSS rescore
  45. 2026-08-05 22:19 UTCEG score recompute
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-03 19:51 UTCEG score recompute
  49. 2026-08-03 10:36 UTCEPSS rescore
  50. 2026-08-02 05:02 UTCEG score recompute
  51. 2026-08-02 02:26 UTCEPSS rescore
  52. 2026-08-01 04:16 UTCEPSS rescore
  53. 2026-07-30 16:27 UTCEPSS rescore
  54. 2026-07-30 01:30 UTCEPSS rescore
  55. 2026-07-28 15:36 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 14:54 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-25 14:17 UTCEPSS rescore
  60. 2026-07-24 14:17 UTCEPSS rescore
  61. 2026-07-23 14:18 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 03:08 UTCEG score recompute
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-21 15:24 UTCEPSS rescore
  68. 2026-07-21 00:17 UTCOSV refresh
  69. 2026-07-20 17:08 UTCEPSS rescore
  70. 2026-07-20 17:08 UTCEPSS rescore
  71. 2026-07-19 14:31 UTCEPSS rescore
  72. 2026-07-19 14:31 UTCEPSS rescore
  73. 2026-07-19 02:29 UTCEPSS rescore
  74. 2026-07-18 10:04 UTCEPSS rescore
  75. 2026-07-18 10:04 UTCEPSS rescore

Related CVEs(same product + same CWE)

Same product

1 shown

PyPI:rucio

Frequently asked(5)

What is CVE-2026-29080?
CVE-2026-29080 is a high vulnerability published on May 6, 2026. A SQL injection vulnerability in FilterEngine.createsqlaquery() allows any authenticated Rucio user to execute arbitrary SQL against the backend database through the DID search endpoint (GET /dids/<scope>/dids/search). On Oracle deployments attacker-controlled filter keys and values are…
When was CVE-2026-29080 disclosed?
CVE-2026-29080 was first published on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-29080 actively exploited?
CVE-2026-29080 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-29080?
CVE-2026-29080 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-29080?
A fix for CVE-2026-29080 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-29080 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-29080

Explore →

Is Your Infrastructure Affected by CVE-2026-29080?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs