Cross-tenant credential leakage in a widely used PostgreSQL admin tool (pgAdmin 4) lets non-owners acquire others' DB credentials and access databases, posing broad risk to enterprise data.
CVE-2026-17349
pgAdmin 4 server clone leaks stored DB credentials to non-owners.
Is CVE-2026-17349 being exploited?
Not confirmed. CVE-2026-17349 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-17349?
CVE-2026-17349 is rated Critical with a CVSS score of 9.3. 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-17349?
Yes. A fix has been recorded for CVE-2026-17349. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17349 affect?
CVE-2026-17349 affects pgAdmin 4 >= 9.0 and < 9.17, Administrators' pgAdmin-managed PostgreSQL servers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17349?
Upgrade to pgAdmin 4 9.17+ and rotate any exposed DB credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Non-owner can clone another user's server entry, inherit stored DB credentials, and access databases with the source user's privileges.
Immediate action required
- affected>= 9.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.