PoC Monitor
← All CVEs
CVE-2026-116247published 30 Oct 2026 19:55 UTCData: JSON · API

pgadmin.org pgAdmin 4

pgAdmin 4: libpq uses the pgAdmin service account's own password file and client certificate

When a server in pgAdmin 4 had no password file, client certificate or client key configured, or the configured one could not be found, pgAdmin left the parameter out of the connection and libpq fell back to the defaults of the operating-system account running pgAdmin: ~/.pgpass, ~/.postgresql/postgresql.crt and postgresql.key, or PGPASSFILE, PGSSLCERT and PGSSLKEY. In server mode any user could therefore connect to a server with the service account's saved passwords or client certificate, and supplying only a copy of its public certificate was enough for libpq to pair it with the service account's private key. A pg_service.conf entry, or a maintenance database name read as a connection string by pg_dumpall, could bring the same files back for the utilities. The fix gives each of these parameters a value in server mode, the user's own file or otherwise a path that can never be opened, in the connection string, in the environment of the utilities and in the --dbname connection string that ranks above a service entry. Desktop mode is unchanged. This issue affects pgAdmin 4: before 9.19.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.6critical · scored by NVD · CWE-522
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

pgadmin.org pgAdmin 4
  • < 9.19

Fixed in 9.19

Mitigation

Upgrade pgAdmin 4 to 9.19 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published30 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.