CVE-2026-116247: pgAdmin 4 · Insufficiently Protected Credentials
Affects pgAdmin 4Source CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 9.19 soon.
Data as of 30 Oct 2026, 20:18 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 user-specific credential files or invalid paths in server mode. No additional action is required if already using version 9.19 or newer. Desktop mode is unaffected by this vulnerability.
Description
CVE-2026-116247 is a vulnerability in pgAdmin 4 before version 9.19 where insufficient protection of credentials in server mode allows any user to connect using the service account's saved passwords or client certificate. This occurs when no password file, client certificate, or client key is configured or found, causing libpq to fall back to default credential files of the operating system account running pgAdmin. The issue is fixed in version 9.19 by ensuring connection parameters explicitly specify user-specific credential files or invalid paths to prevent unauthorized access.