CVE-2026-7815

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 64% 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.

SQL injection vulnerability in pgAdmin 4 Maintenance Tool.

Four user-supplied JSON fields (buffer_usage_limit, vacuum_parallel, vacuum_index_cleanup, reindex_tablespace) were concatenated directly into the rendered VACUUM/ANALYZE/REINDEX command and passed to psql --command. An authenticated user with the tools_maintenance permission could break out of the option syntax and execute arbitrary SQL on the connected PostgreSQL server. The injected SQL could in turn invoke COPY ... TO PROGRAM to escalate to operating-system command execution on the database host.

Fix introduces server-side allow-listing of all four fields and switches reindex_tablespace from manual quoting to the qtIdent filter.

This issue affects pgAdmin 4: before 9.15.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
36.6%
KEV
Not listed

Published

May 11, 2026

Last Modified

May 26, 2026

Advisory Details (1)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

SQL injection in Maintenance tool option values (CVE-2026-7815) · Issue #9898 · pgadmin-org/pgadmin4 · GitHub

https://github.com/pgadmin-org/pgadmin4/issues/9898

Vendor Advisories for CVE-2026-7815(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
pgadmin44.20 ... 9.9 (77 versions)9.15

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 48× 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.

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

Frequently asked(5)

What is CVE-2026-7815?
CVE-2026-7815 is a high vulnerability published on May 11, 2026. SQL injection vulnerability in pgAdmin 4 Maintenance Tool. Four user-supplied JSON fields (bufferusagelimit, vacuumparallel, vacuumindexcleanup, reindextablespace) were concatenated directly into the rendered VACUUM/ANALYZE/REINDEX command and passed to psql --command. An authenticated user with…
When was CVE-2026-7815 disclosed?
CVE-2026-7815 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7815 actively exploited?
CVE-2026-7815 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7815?
CVE-2026-7815 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-7815?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7815, 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-7815

Explore →

Is Your Infrastructure Affected by CVE-2026-7815?

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