SQL injection via unescaped database object names
Published Jul 31, 2026 · Updated Jul 31, 2026
SQL injection in pgAdmin 4 before 9.17 allows remote authenticated users to execute SQL through crafted database object names. Index Statistics and publication or subscription dependency templates insert pg_catalog names into quoted SQL literals without qtLiteral escaping. A low-privileged database role can plant an apostrophe-bearing name; opening the affected view executes stacked statements with the viewer's database privileges.
Summary
What happened
SQL injection in pgAdmin 4 before 9.17 allows remote authenticated users to execute SQL through crafted database object names. Index Statistics and publication or subscription dependency templates insert pg_catalog names into quoted SQL literals without qtLiteral escaping. A low-privileged database role can plant an apostrophe-bearing name; opening the affected view executes stacked statements with the viewer's database privileges.
The record
- CVE
- CVE-2026-17346
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- pgAdmin Development Team
- Product
- pgAdmin 4
- Classifications
- CWE-89
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0 <9.17
- Affected versionversion=5.0 <9.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo