CVE-2026-29090

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 82% 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Summary

A SQL injection vulnerability exists in Rucio versions 1.30.0 and later before 35.8.5, 38.5.5, 39.4.2, and 40.1.1, in FilterEngine.create_postgres_query(). This allows any authenticated Rucio user to execute arbitrary SQL against the PostgreSQL metadata database through the DID search endpoint (GET /dids//dids/search). When the postgres_meta metadata plugin is configured, attacker-controlled filter keys and values are interpolated directly into raw SQL strings via Python .format(), then passed to psycopg3's sql.SQL() which treats the string as trusted SQL syntax.

Depending on the database privileges assigned to the service account, exploitation can expose sensitive tables, modify or delete metadata, access server-side files, or achieve code execution through PostgreSQL features such as COPY ... FROM PROGRAM. This issue affects deployments that explicitly use the postgres_meta metadata 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.8(medium)
EPSS
21.9%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (1)

Auto-updated May 6, 2026
Patch available. Sources: github.
github Patch Available

SQL Injection in External PostgreSQL Metadata Plugin via DID Search API · Advisory · rucio/rucio · GitHub

https://github.com/rucio/rucio/security/advisories/GHSA-6j7p-qjhg-9947

Vendor Advisories for CVE-2026-29090(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 rangeFixed inDependents
rucio40.0.0, 40.1.040.1.1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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 113 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-29090?
CVE-2026-29090 is a high vulnerability published on May 6, 2026. Summary A SQL injection vulnerability exists in Rucio versions 1.30.0 and later before 35.8.5, 38.5.5, 39.4.2, and 40.1.1, in FilterEngine.createpostgresquery(). This allows any authenticated Rucio user to execute arbitrary SQL against the PostgreSQL metadata database through the DID search…
When was CVE-2026-29090 disclosed?
CVE-2026-29090 was first published in the National Vulnerability Database 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-29090 actively exploited?
CVE-2026-29090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-29090?
CVE-2026-29090 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-29090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-29090, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-29090?

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