CVE-2026-17346
SQL injection in pgAdmin 4 templates allows arbitrary SQL in a viewing user's DB session.
Is CVE-2026-17346 being exploited?
Not confirmed. CVE-2026-17346 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-17346?
CVE-2026-17346 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-17346?
Yes. A fix has been recorded for CVE-2026-17346. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17346 affect?
CVE-2026-17346 affects pgAdmin 4 < 9.17 (Index Statistics template from 1.0), pgAdmin 4 < 9.17 (Publications/Subscriptions templates from 5.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17346?
Upgrade to pgAdmin 9.17; restrict CREATE TABLE/PUBLICATION/SUBS privileges until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Low-priv user can create quoted object names with apostrophes to inject arbitrary SQL in any user who opens stats/dependencies, enabling data exfiltration or privilege escalation.
Immediate action required
- affected>= 1.0 and < 9.17
- affected>= 5.0 and < 9.17
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.