pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file
Source GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 9.19 soon.
Data as of 30 Oct 2026, 23:27 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 8.2 |
|---|---|---|
| CNA (PostgreSQL) | CVSS 4.0 | 7.1 |
- Patch
- Available – fixed in 9.19
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade pgAdmin 4 to 9.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pgadmin.orgpgAdmin 4 | Affected
| Fixed in
|
GitHubpgAdmin 4pkg:github/pgAdmin 4Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade pgAdmin 4 to version 9.19 or later, where the vulnerability is fixed by restricting SSH tunnel authentication to user-configured identity files or passwords only. Do not rely on the service account's SSH keys or ssh-agent in server mode tunnels. Desktop mode is unaffected and requires no change. No other mitigation is indicated by the vendor advisory.
Description
pgAdmin 4 versions before 9.19 have a vulnerability in server mode SSH tunnel handling. The application used the sshtunnel library without restricting it to user-configured identity files, causing it to load unencrypted private keys and SSH configuration from the service account's ~/.ssh directory. This allowed any user to configure a tunnel using the service account's SSH keys and agent, potentially accessing hosts that accept those keys without their own credentials. The issue is fixed in version 9.19 by restricting tunnel authentication to only user-configured identity files or passwords, preventing fallback to the service account's SSH keys and configuration. Desktop mode remains unaffected.