CVE-2026-17346 is a SQL injection vulnerability in pgAdmin 4 caused by unsafe interpolation of database object names into SQL templates. After the earlier hardening for CVE-2026-12044, several sinks remained vulnerable because schema, table, publication, and subscription names obtained from pg_catalog were incorrectly assumed to be inherently safe and were left on an allowlist. PostgreSQL permits arbitrary characters in quoted identifiers, including apostrophes, so an attacker can create an object with a crafted name that breaks out of raw '{{ name }}' interpolation when pgAdmin renders affected queries. The vulnerable sinks include the all-indexes Index Statistics query in coll_stats.sql for both the 16_plus and default PostgreSQL template variants, as well as publication and subscription dependencies and position templates, including PostgreSQL and EPAS dialect variants for publications. When a user opens the affected object's Statistics or Dependencies tab, the injected SQL executes in that user's database session. The issue affects the Index Statistics sink from pgAdmin 4 1.0 onward and the Publications and Subscriptions sinks from 5.0 onward, through versions before 9.17.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.