Read the docs
TI-2026-83353 Aliases CVE-2026-116239GHSA-mv93-hq32-623f

pgAdmin 4 LDAP or Kerberos login opens another account by username

Priority MEDIUM 41CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-287.

Summary

In server mode, pgAdmin 4 before 9.19 logs a user authenticated by LDAP or Kerberos into an internal account with the same username, including the administrator account. The login picks the account by username alone and does not check which source authenticated the user (CWE-287). Someone with valid LDAP or Kerberos credentials that pgAdmin is configured to use gains that account's role, servers and saved database passwords. Desktop mode is not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-10-31

Description from the CNA

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, with its role, its servers and its saved database passwords: - An LDAP or Kerberos user whose username matched an internal account was logged in as that internal account, including the administrator account created when pgAdmin is first set up. - With internal authentication listed before LDAP or Kerberos in AUTHENTICATION_SOURCES, the login form's internal validation looks up the account whose email was typed and keeps it even though its password does not match. A Kerberos user could type another Kerberos user's principal and be logged in as that user, and an LDAP user could do the same with an LDAP account whose email is their username. Exploitation requires valid credentials for an LDAP directory or Kerberos realm that pgAdmin is configured to use. The fix looks the account up by the authenticated username and the source that authenticated it, and no longer uses the account the login form found for any source but internal authentication. Internal authentication logs in that account only if it is an internal account. Desktop mode is not affected. This issue affects pgAdmin 4: before 9.19.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00403 34th percentileScored 2026-11-07
Fix Fixed pgAdmin 4 (pgadmin.org): 9.19

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
pgadmin.orgpgAdmin 4before 9.199.19Patch availableCNA
  • pgAdmin 4 Vendorpgadmin.org Affected before 9.19 Fixed in 9.19 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:*:*:*before 9.19Vulnerablepgadmin.org
  • cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:*:*:* Versions before 9.19 Vulnerable ·pgadmin.org

Remediation

Fixed in pgAdmin 4 9.19, so upgrade to that version or later.

Written with Claude Haiku 5.5 from the sources below · 2026-10-31

  • Fix · CNA pgAdmin 4 (pgadmin.org) Fixed in 9.19

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    pgadmin.org pgAdmin 4 9.19

    15 records Highest priority Priority MEDIUM 3 MEDIUM, 12 LOW

    Other records, highest priority first

    • TI-2026-83355 Command execution via backslash bypass in pgAdmin 4 query exportPriority MEDIUM 42
    • TI-2026-83352 Failed login limit bypass in pgAdmin 4 allows unlimited password guessingPriority MEDIUM 42
    • TI-2026-83357 Utility binary path in pgAdmin 4 can point at shared storagePriority LOW 36
    Show all 15 records →

Timeline

  1. 2026-10-30 Threatist record created from CVE-2026-116239
  2. 2026-10-30 Alias added: GHSA-mv93-hq32-623f
  3. 2026-11-01 Priority changed: MEDIUM → LOW
  4. 2026-11-04 CVSS score added · NVD
  5. 2026-11-06 CISA SSVC decision points changed
  6. 2026-11-06 Priority changed: LOW → MEDIUM

References

Patch 2

Other 1

  • TI-2024-01901 Unsafe Deserialisation and Remote Code Execution by an Authenticated user in pgAdmin 4 CVSS 3.1CRITICAL 9.9
  • TI-2024-02918 Remote Code Execution Vulnerability through the validate binary path API in pgAdmin 4 CVSS 3.1CRITICAL 9.8
  • TI-2022-03867 Code injection in pgadmin4 CVSS 3.1HIGH 8.8
  • TI-2026-06875 pgAdmin 4: Cross-user data access and shared-server privilege escalation in server mode CVSS 4.0CRITICAL 9.4
  • TI-2025-02572 pgAdmin 4: Remote Code Execution in Query Tool and Cloud Deployment CVSS 3.1CRITICAL 9.9
  • TI-2023-00228 Path traversal in pgadmin CVSS 3.1MEDIUM 6.5
See all 56 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences