Live › vulnerability › CVE-2026-116247
When a pgAdmin 4 server entry lacked a password file, client certificate or key, libpq fell back to the service account's default files on the host. In server mode, any pgAdmin user could then connect using the service account's saved passwords or client certificate, or pair a copied public certificate with its private key.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 20:25 UTC. All times on this page are UTC.
Only pgAdmin 4 deployments running in server mode are exposed, where multiple users share one pgAdmin instance. Exposure depends on the service account running pgAdmin having a password file or client certificate in its home directory, or a pg_service.conf entry. Desktop mode is unchanged according to the sources.
No product ranges from the sources yet.
pgadmin4 --version or the About dialog; affected versions are before 9.19.~/.pgpass, ~/.postgresql/postgresql.crt and postgresql.key in the home directory of the account running pgAdmin.9.19 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-116247")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.