PatchTheCVECVE-2026-116239: In server mode pgAdmin 4 keeps an account per authentication source, so the same username can exist as, for ex
CVE-2026-116239 is a high-severity flaw (CVSS 8.5) affecting pgadmin 4. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
In server mode pgAdmin 4 keeps an account per authentication source, so the same username can exist as, for example, an internal account and an LDAP account. After LDAP or Kerberos authenticated a user, pgAdmin chose the account to log in by username alone, or took the account Flask-Security's login form had looked up, without checking that it came from the source that authenticated the user. The session therefore belonged to another account, wit
Why this priority
- High severity
- Covered by 3 security sources
A fixed release or distro patch exists.
Last updated 2026-11-04 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Advisories and coverage
Official advisories
- PostgreSQL Security: pgAdmin 4 v9.19 Released 2026-10-31
Research and news
- VulDB Recent Entries: CVE-2026-116239 | pgAdmin up to 9.18 Server Mode improper authentication 2026-10-30
- Vulners Bulletins: CVE-2026-116239 2026-10-30
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-116239?
pgadmin 4: upgrade to 9.19. Exact commands for each OS are on this page.
Is CVE-2026-116239 being exploited?
CVE-2026-116239 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-116239 affect?
CVE-2026-116239 affects pgadmin 4. Severity is high (CVSS 8.5). In server mode pgAdmin 4 keeps an account per authentication source, so the same username can exist as, for example, an internal account and an LDAP account. After LDAP or Kerberos authenticated a user, pgAdmin chose the account to log in b
How urgent is CVE-2026-116239?
Priority 41/100. High severity; Covered by 3 security sources
Software pages
Related CVEs
- CVE-2026-116241 CRITICAL 9.9 UPGRADE pgAdmin 4's Import/Export Data tool wraps a user's query export in a psql \copy (...) TO command and checks th
- CVE-2026-116240 MEDIUM 6.5 UPGRADE In server mode pgAdmin 4 validates a path into the user's storage directory with check_access_permission(), wh
- CVE-2026-116242 HIGH 8.2 UPGRADE pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_confi
- CVE-2026-116243 HIGH 7.5 UPGRADE pgAdmin 4 runs pg_dump, pg_restore, pg_dumpall and psql from the binary path a user sets in their preferences
- CVE-2026-116244 HIGH 8.2 UPGRADE When a pgAdmin 4 connection was not meant to use a Kerberos user's delegated credentials, pgAdmin removed KRB5