Skip to main content
CVE-2026-116251VulnerabilityPublished

pgAdmin 4 did not invalidate a user's existing sessions when their password changed, either through the user's own

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116251· Medium 4.2

Not known to be exploited · CVSS 4.2 Medium : upgrade to 9.19 when convenient.

Data as of 30 Oct 2026, 23:22 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PostgreSQL)CVSS 3.14.2
CNA (PostgreSQL)CVSS 4.02.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
pgadmin.orgpgAdmin 4Affected
  • <9.19
Fixed in
  • 9.19
GitHubpgAdmin 4pkg:github/pgAdmin 4Other threatsAffected
  • <9.19
Fixed in
  • 9.19

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.

References

Community reviews

Loading reviews…