CVE-2026-17346: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in pgadmin.org pgAdmin 4
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.
AI Analysis
Technical Summary
This vulnerability in pgAdmin 4 involves improper neutralization of special elements used in SQL commands (CWE-89). Specifically, the fix for CVE-2026-12044 hardened some templates but missed several sinks where object names sourced from pg_catalog could contain apostrophes. Because PostgreSQL allows arbitrary characters in quoted identifiers, a low-privileged user able to create tables, publications, or subscriptions can insert apostrophes in object names that break out of unescaped template interpolation. This leads to arbitrary SQL injection in the database session of any user viewing the affected object's statistics or dependencies. The affected sinks include the Index Statistics query for all-indexes listing and publication/subscription dependencies templates. The fix involves switching these templates to use qtLiteral for proper escaping and updating code to pass the database connection for quoting. The vulnerability affects pgAdmin 4 versions from 1.0 through 9.16.
Potential Impact
Successful exploitation allows a low-privileged user to inject arbitrary SQL statements into the database session of a higher-privileged user viewing certain statistics or dependencies tabs in pgAdmin 4. This can lead to full compromise of confidentiality, integrity, and availability of the database managed via pgAdmin 4. The CVSS score of 8.8 (high) reflects the network attack vector, low attack complexity, low privileges required, no user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed in pgAdmin 4 version 9.17 by properly escaping all affected templates using qtLiteral and updating code to pass the database connection for quoting. Users should upgrade to version 9.17 or later to remediate this issue. Until patched, avoid opening the Statistics or Dependencies tabs for objects created by low-privileged users with potentially malicious names.
CVE-2026-17346: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in pgadmin.org pgAdmin 4
Description
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.1
Score 8.8high
Affected software
pgadmin.org
pgAdmin 4
pgadmin.org
pgAdmin 4
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in pgAdmin 4 involves improper neutralization of special elements used in SQL commands (CWE-89). Specifically, the fix for CVE-2026-12044 hardened some templates but missed several sinks where object names sourced from pg_catalog could contain apostrophes. Because PostgreSQL allows arbitrary characters in quoted identifiers, a low-privileged user able to create tables, publications, or subscriptions can insert apostrophes in object names that break out of unescaped template interpolation. This leads to arbitrary SQL injection in the database session of any user viewing the affected object's statistics or dependencies. The affected sinks include the Index Statistics query for all-indexes listing and publication/subscription dependencies templates. The fix involves switching these templates to use qtLiteral for proper escaping and updating code to pass the database connection for quoting. The vulnerability affects pgAdmin 4 versions from 1.0 through 9.16.
Potential Impact
Successful exploitation allows a low-privileged user to inject arbitrary SQL statements into the database session of a higher-privileged user viewing certain statistics or dependencies tabs in pgAdmin 4. This can lead to full compromise of confidentiality, integrity, and availability of the database managed via pgAdmin 4. The CVSS score of 8.8 (high) reflects the network attack vector, low attack complexity, low privileges required, no user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed in pgAdmin 4 version 9.17 by properly escaping all affected templates using qtLiteral and updating code to pass the database connection for quoting. Users should upgrade to version 9.17 or later to remediate this issue. Until patched, avoid opening the Statistics or Dependencies tabs for objects created by low-privileged users with potentially malicious names.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- PostgreSQL
- Date Reserved
- 2026-07-25T02:52:54.197Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a6cf74dbf32cb7a34294af8
Added to database: 07/31/2026, 19:28:13 UTC
Last enriched: 07/31/2026, 19:39:34 UTC
Last updated: 09/13/2026, 22:01:32 UTC
Views: 58
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.