CVE-2026-116239

pgAdmin 4: An LDAP or Kerberos login is logged in to another account with the same username

Published Oct 30, 2026 CVSS 4.0 · 8.9 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The flaw occurs when pgAdmin 4 in server mode selects a user account solely by username after an LDAP or Kerberos authentication, without verifying that the authenticated source matches the account’s origin. An attacker with valid LDAP or Kerberos credentials that match a username already defined as an internal account can be logged in as that internal account, potentially an administrator. This gives the attacker that account’s roles, access to all configured servers, and stored database passwords, effectively providing full read/write privileges to all managed databases, a serious authentication bypass problem formally identified as CWE‑287 and CWE‑639.

Affected Systems

The affected product is pgAdmin 4, the open‑source PostgreSQL administration tool, for all releases prior to version 9.19. The vulnerability is present only in the server mode of pgAdmin and does not apply to the desktop mode.

Risk and Exploitability

The CVSS score of 8.9 indicates high severity. Exploitation requires possession of valid LDAP or Kerberos credentials that the deployed pgAdmin instance is configured to use, and the attack is limited to server mode. The EPSS value is not available, but the combination of high CVSS and the potential for complete privilege escalation suggests a significant risk. The vulnerability is not listed in the CISA KEV catalogue, indicating no confirmed widespread exploitation yet, yet it remains a high‑risk issue for all organizations running vulnerable versions of pgAdmin 4.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to pgAdmin 4 version 9.19 or later, where the authentication source is correctly verified during login.
  • Reconfigure the AUTHENTICATION_SOURCES setting so that internal authentication is listed after LDAP or Kerberos sources to prevent accidental account reuse.
  • Restrict or disable LDAP and Kerberos authentication for accounts that do not require it, limiting the ability to log in as privileged internal users through external credentials.

Generated by OpenCVE AI on October 30, 2026 at 21:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Pgadmin
Pgadmin pgadmin 4
Vendors & Products Pgadmin
Pgadmin pgadmin 4
Type Values Removed Values Added
Description 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.
Title pgAdmin 4: An LDAP or Kerberos login is logged in to another account with the same username
Weaknesses CWE-287
CWE-639
References
Metrics cvssV3_1

{'score': 8.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.9, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N'}

Weaknesses
  • CWE-287

    Improper Authentication

  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
PostgreSQL
Published
Updated
Nov 6, 2026, 4:08 PM
Reserved
Oct 25, 2026, 4:26 PM
Status
Analyzed
Published
Oct 30, 2026, 8:17 PM
Modified
Nov 6, 2026, 4:17 PM