CVE-2026-17346

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH 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%CVSS: 8.8Exploit: None knownExposed: 0

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

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.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

July 31, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 31, 2026
Upstream fix merged — awaiting tagged release. 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 26× in last 7d / 85× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:02 UTCGHSA enrichment
  3. 2026-08-20 07:44 UTCGHSA enrichment
  4. 2026-08-19 19:26 UTCEG score recompute
  5. 2026-08-19 19:26 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 06:48 UTCGHSA enrichment
  8. 2026-08-18 18:26 UTCEG score recompute
  9. 2026-08-18 18:26 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 03:42 UTCGHSA enrichment
  12. 2026-08-17 15:24 UTCEG score recompute
  13. 2026-08-17 15:24 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 03:06 UTCEG score recompute
  16. 2026-08-17 03:06 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:48 UTCGHSA enrichment
  19. 2026-08-16 02:30 UTCEG score recompute
  20. 2026-08-16 02:30 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 14:13 UTCGHSA enrichment
  23. 2026-08-15 01:55 UTCEG score recompute
  24. 2026-08-15 01:55 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 60 more
  1. 2026-08-14 13:38 UTCGHSA enrichment
  2. 2026-08-14 01:20 UTCEG score recompute
  3. 2026-08-14 01:20 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 13:02 UTCGHSA enrichment
  6. 2026-08-13 00:44 UTCEG score recompute
  7. 2026-08-13 00:44 UTCGHSA enrichment
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-12 12:27 UTCGHSA enrichment
  10. 2026-08-12 00:09 UTCEG score recompute
  11. 2026-08-12 00:09 UTCGHSA enrichment
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 11:51 UTCEG score recompute
  14. 2026-08-11 11:51 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 23:33 UTCGHSA enrichment
  17. 2026-08-10 11:14 UTCGHSA enrichment
  18. 2026-08-09 22:56 UTCEG score recompute
  19. 2026-08-09 22:56 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 10:38 UTCGHSA enrichment
  22. 2026-08-08 22:21 UTCEG score recompute
  23. 2026-08-08 22:21 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 10:03 UTCGHSA enrichment
  26. 2026-08-07 21:46 UTCEG score recompute
  27. 2026-08-07 21:46 UTCGHSA enrichment
  28. 2026-08-07 09:28 UTCGHSA enrichment
  29. 2026-08-06 21:10 UTCEG score recompute
  30. 2026-08-06 21:10 UTCGHSA enrichment
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-06 08:52 UTCGHSA enrichment
  33. 2026-08-05 20:34 UTCEG score recompute
  34. 2026-08-05 20:34 UTCGHSA enrichment
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-05 14:11 UTCGHSA enrichment
  37. 2026-08-05 00:53 UTCEG score recompute
  38. 2026-08-05 00:52 UTCGHSA enrichment
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 12:34 UTCEG score recompute
  41. 2026-08-04 12:34 UTCGHSA enrichment
  42. 2026-08-04 10:38 UTCEPSS rescore
  43. 2026-08-04 07:25 UTCGHSA enrichment
  44. 2026-08-03 19:05 UTCEG score recompute
  45. 2026-08-03 19:05 UTCGHSA enrichment
  46. 2026-08-03 10:35 UTCEPSS rescore
  47. 2026-08-03 06:47 UTCGHSA enrichment
  48. 2026-08-02 18:28 UTCGHSA enrichment
  49. 2026-08-02 06:10 UTCEG score recompute
  50. 2026-08-02 06:09 UTCGHSA enrichment
  51. 2026-08-02 02:26 UTCEPSS rescore
  52. 2026-08-01 17:49 UTCGHSA enrichment
  53. 2026-08-01 05:31 UTCEG score recompute
  54. 2026-08-01 05:31 UTCGHSA enrichment
  55. 2026-08-01 04:48 UTCEG score recompute
  56. 2026-08-01 04:48 UTCGHSA enrichment
  57. 2026-07-31 18:19 UTCEG score recompute
  58. 2026-07-31 17:34 UTCEG score recompute
  59. 2026-07-31 16:21 UTCEG score recompute
  60. 2026-07-31 16:18 UTCMITRE cvelistV5first tracked

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 64.4% of all scored CVEs.
What is the CVSS score of CVE-2026-17346?
CVE-2026-17346 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-17346?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17346, 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

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.