pgAdmin 4 did not invalidate a user's existing sessions when their password changed, either through the user's own
Source GCVE Database
Not known to be exploited · CVSS 4.2 Medium : upgrade to 9.19 when convenient.
Data as of 30 Oct 2026, 23:22 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 4.2 |
|---|---|---|
| CNA (PostgreSQL) | CVSS 4.0 | 2.3 |
- Patch
- Available – fixed in 9.19
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/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 issue is fixed by session identifier rotation on password changes. This ensures all other sessions are logged out and saved passwords are securely re-encrypted. There is no indication that temporary workarounds are effective; applying the official fix is recommended.
Description
pgAdmin 4 versions prior to 9.19 did not invalidate existing user sessions when a password was changed, either by the user or an administrator. This allowed sessions established before the password change to remain active until they expired, potentially allowing continued access by unauthorized parties. The issue was fixed by rotating the user's session identifier upon password change, logging out all other sessions and re-encrypting saved server passwords under the new key.