CVE-2026-17346

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-31. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
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.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The fix for CVE-2026-12044 in pgAdmin 4 9.16 hardened qtLiteral and switched sixteen COMMENT ON / pgstattuple / pgstatindex templates to it, but missed several sinks that had been placed in test_sql_string_literal_lint.py's ALLOWLIST on the incorrect assumption that schema, table, publication, and subscription names sourced from pg_catalog via the browser tree could never contain an apostrophe. PostgreSQL permits arbitrary characters in quoted identifiers, so a low-privileged user able to CREATE TABLE, CREATE PUBLICATION, or CREATE SUBSCRIPTION can plant an apostrophe'd object name that breaks out of the unescaped '{{ name }}' template interpolation the moment any user (including a higher-privileged one) opens that object's Statistics or Dependencies tab, allowing arbitrary SQL statement injection in the viewing user's database session.

Affected sinks: the Index Statistics query for all-indexes listing (coll_stats.sql, both the 16_plus and default PostgreSQL-version template variants -- distinct from the single-index stats.sql path already fixed in CVE-2026-12044), and the publication and subscription dependencies.sql / get_position.sql templates (both the pg and ppas/EPAS dialect variants for publications).

Fix switches all of these templates to qtLiteral(conn) for name interpolation, and updates publications/__init__.py and subscriptions/__init__.py to pass conn=self.conn into the dependencies.sql render_template call so the qtLiteral filter has a connection to quote against. The corresponding ALLOWLIST entries in test_sql_string_literal_lint.py are removed now that these sinks are properly escaped rather than merely assumed safe. A behavioral regression test renders each fixed template with a stacked-statement apostrophe payload and asserts both that the object name appears exactly as qtLiteral-escaped and that the rendered SQL parses as exactly one statement, verifying the assertion genuinely fails against the pre-patch raw-interpolation form.

This issue affects pgAdmin 4: the Index Statistics sink from 1.0, and the Publications/Subscriptions sinks from 5.0, both before 9.17.

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

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%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 31, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 31, 2026
Patch available. Sources: github_commit.
generic

SQL injection via unescaped object names in index Statistics and publication/subscription dependency views (CVE-2026-17346) · Issue #10193 · pgadmin-org/pgadmin4 · GitHub

https://github.com/pgadmin-org/pgadmin4/issues/10193
github_commit

commit f75452bfd0f7 (pgadmin-org/pgadmin4)

Fix landed in pgadmin-org/pgadmin4 commit f75452bfd0f7 — awaiting tagged release

https://github.com/pgadmin-org/pgadmin4/commit/f75452bfd0f786d0c071638919d48fc1d76f987d
github_commit

commit 73b3218992cc (pgadmin-org/pgadmin4)

Fix landed in pgadmin-org/pgadmin4 commit 73b3218992cc — awaiting tagged release

https://github.com/pgadmin-org/pgadmin4/commit/73b3218992cc37af6e10b7e54eaeed6ec293c6b2

Vendor Advisories for CVE-2026-17346(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 79× 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 213 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-17346?
CVE-2026-17346 is a high vulnerability published on July 31, 2026. The fix for CVE-2026-12044 in pgAdmin 4 9.16 hardened qtLiteral and switched sixteen COMMENT ON / pgstattuple / pgstatindex templates to it, but missed several sinks that had been placed in testsqlstringliterallint.py's ALLOWLIST on the incorrect assumption that schema, table, publication, and…
When was CVE-2026-17346 disclosed?
CVE-2026-17346 was first published on July 31, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17346 actively exploited?
CVE-2026-17346 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17346?
CVE-2026-17346 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-17346?
A fix for CVE-2026-17346 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17346 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-17346

Explore →

Is Your Infrastructure Affected by CVE-2026-17346?

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