pgAdmin · When a Server
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 this issue is fixed by explicitly setting connection parameters to prevent fallback to the service account's credentials. No additional action is required if the upgrade is applied. If upgrading is not immediately possible, restrict access to the server mode environment to trusted users only to minimize risk.
Description
pgAdmin 4 versions before 9.19 had a vulnerability where, if no password file, client certificate, or client key was configured or found, the connection would fall back to using the operating system account's saved credentials. This allowed any user in server mode to connect using the service account's saved passwords or client certificate by supplying only the public certificate. The issue was fixed by explicitly setting these parameters to the user's own files or to inaccessible paths in server mode, preventing unintended credential use.