Quick answers
- Is CVE-2026-116247 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116247 being exploited in the wild.
- How severe is CVE-2026-116247?
- High severity, with a CVSS score of 8.2, published 30 October 2026.
- Which products and versions are affected?
- pgAdmin Project pgAdmin 4 before 9.19.
- Is there a fix for CVE-2026-116247?
- Yes: fixed in pgAdmin 4 9.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116247 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116247?
- Check whether you run pgAdmin Project pgAdmin 4 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: pgAdmin 4 9.19
Technical details
When pgAdmin 4 server mode lacks configured password files, client certificates, or client keys, the libpq connection library falls back to OS-level defaults (~/.pgpass, ~/.postgresql/postgresql.crt, PGPASSFILE, PGSSLCERT, PGSSLKEY). Any pgAdmin user can exploit this to connect as the service account; supplying a public certificate is sufficient for libpq to pair it with the service account's private key. The vulnerability affects server mode; desktop mode is unaffected.
Affected products
- pgAdmin Project pgAdmin 4 before 9.19
Timeline
- 2026-10-30: disclosed