Skip to main content
VulnerabilityPublished

CVE-2026-116239: pgAdmin 4 · Improper Authentication

Affects pgAdmin 4Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 9.19 soon.

Data as of 30 Oct 2026, 20:38 UTC

CVSS 3.1 base score
8.5High
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.18.5
CNA (PostgreSQL)CVSS 4.08.9
Patch
Available – fixed in 9.19
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

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 vulnerability is fixed by verifying both the authenticated username and the authentication source before establishing a session. No other mitigation is required as the fix addresses the root cause. Desktop mode users are not affected and do not require action.

Description

CVE-2026-116239 is an improper authentication vulnerability in pgAdmin 4 server mode before version 9.19. It allows an LDAP or Kerberos authenticated user to be logged in as a different account if usernames overlap across authentication sources, potentially gaining access to another user's roles, servers, and saved database passwords. The flaw arises because pgAdmin selects the account to log in by username alone or by the login form's lookup without verifying the authentication source. This issue does not affect desktop mode and requires valid LDAP or Kerberos credentials to exploit.

References

Community reviews

Loading reviews…