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

pgadmin.org pgAdmin 4

pgAdmin 4: SSH tunnels use the pgAdmin service account's own SSH identity

pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file, so it always loaded the unencrypted private keys in ~/.ssh of the operating-system account running pgAdmin, read that account's ~/.ssh/config (IdentityFile, User, HostName, ProxyCommand) for the tunnel host, and could use its ssh-agent. In server mode any user could therefore configure a tunnel to a host that accepts the service account's key, with no credentials of their own or with an identity file that did not exist in their storage, and reach it as that account. The fix makes tunnels in server mode use only the identity file or password the user configured: the service account's keys, configuration and agent are no longer used, and an identity file that cannot be found in the user's storage is reported instead of falling back to ~/.ssh. 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.