CVE-2026-116242

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

State
Published
Severity
7.1 High
Published
Oct 30, 2026
Updated
Oct 30, 2026
Reserved
Oct 25, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
4.07.1 HighCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:NPostgreSQL
3.18.2 HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:NPostgreSQL

Weaknesses

  • CWE-522 Insufficiently Protected Credentials
  • CWE-1188 Initialization of a Resource with an Insecure Default

Affected Products

ProductVersions
pgAdmin 4pgadmin.org
  • before 9.19Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.