CVE-2026-116247
Last modified
CVE-2026-116247 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. 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.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| pgadmin.org | pgAdmin 4 | < 9.19 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-116247?
How severe is CVE-2026-116247?
How do I fix CVE-2026-116247?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-116241pgAdmin 4's Import/Export Data tool wraps a user's query exp…9.9
- CVE-2026-116242pgAdmin 4 opens SSH tunnels with the sshtunnel library but g…8.2
- CVE-2026-116243pgAdmin 4 runs pg_dump, pg_restore, pg_dumpall and psql from…7.5
- CVE-2026-116244When a pgAdmin 4 connection was not meant to use a Kerberos …8.2
- CVE-2026-116245libpq looks a connection service up in the service file of t…8.2
- CVE-2026-116246To pass a server's password to psql and to the utilities pgA…6.5
- CVE-2026-116248In pgAdmin 4 server mode only administrators are meant to sh…6.8
- CVE-2026-116249In server mode pgAdmin 4 resolves a server's password file, …8.4
- CVE-2026-11625Bytes::Random::Secure versions through 0.29 for Perl share i…7.5
- CVE-2026-116250In server mode pgAdmin 4 validates a path a user gives for a…6.5
- CVE-2026-116251pgAdmin 4 did not invalidate a user's existing sessions when…4.2
- CVE-2026-116252pgAdmin 4's materialized view refresh passed the target data…6.5
Are you affected by CVE-2026-116247?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
