Quick answers
- Is CVE-2026-116242 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116242 being exploited in the wild.
- How severe is CVE-2026-116242?
- High severity, with a CVSS score of 8.2, published 30 October 2026.
- Which products and versions are affected?
- Pgadmin 4 before 9.19.
- Is there a fix for CVE-2026-116242?
- 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-116242 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116242?
- Check whether you run 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
The sshtunnel library was initialized without host_pkey_directories or ssh_config_file parameters, causing it to fall back to the operating system account's ~/.ssh directory for unencrypted private keys and ~/.ssh/config settings. In server mode, any user could configure a tunnel to a host accepting the service account's key without supplying their own credentials or identity file. The fix restricts server-mode tunnels to only user-configured identity files or passwords, removing access to the service account's keys, configuration, and ssh-agent.
Affected products
- pgAdmin pgAdmin 4 before 9.19
Timeline
- 2026-10-30: disclosed
- 2026-10-24: patched