Skip to content
EXYS
Back to the CVEs

CVE-2026-116239

8.8, high

Pgadmin.org pgAdmin 4 Improper Authentication Vulnerability

CVSS
8.8, high high CVSS v3.1
EPSS, next 30 days
0.4% higher than 33.1% of scored CVEs
Exploitation
No public evidence
Published
30 Oct 20266 days ago

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.

Details

Vendor
Pgadmin.org
Product
pgAdmin 4
Weakness
CWE-287 (opens in a new tab)
Status
Analyzed
Updated
4 Nov 2026
Assigner
f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References 3

The kind is read from NVD's tags where present and from the shape of the URL otherwise, so treat it as a hint.

Other Pgadmin.org CVEs

Every Pgadmin.org CVE we hold

Same vendor in what we hold, not a known link between the flaws.

  • CVE-2026-116242 Pgadmin.org pgAdmin 4 Insufficiently Protected Credentials Vulnerability EPSS 0.2% 9.6, critical
  • CVE-2026-116244 Pgadmin.org pgAdmin 4 Insufficiently Protected Credentials Vulnerability EPSS 0.3% 9.6, critical
  • CVE-2026-116245 Pgadmin.org pgAdmin 4 Insufficiently Protected Credentials Vulnerability EPSS 0.2% 9.6, critical
  • CVE-2026-116247 Pgadmin.org pgAdmin 4 Insufficiently Protected Credentials Vulnerability EPSS 0.1% 9.6, critical
  • CVE-2026-116241 Pgadmin.org pgAdmin 4 OS Command Injection Vulnerability EPSS 0.3% 8.8, high
  • CVE-2026-116243 Pgadmin.org pgAdmin 4 Untrusted Search Path Vulnerability EPSS 0.3% 8.8, high
  • CVE-2026-116246 To pass a server's password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into… EPSS 0.2% 7.6, high

Beyond this page

Is CVE-2026-116239 in your network?

This page tells you how dangerous CVE-2026-116239 is out there. Whether it sits on one of your devices, only a scan of your own network can tell. That is what our systems do, every day, for the companies we protect.

  • EXYS7600 OCELOT

    Find it before attackers do

    Ocelot scans your network on a schedule and reports every vulnerability it finds by its CVE identifier, with its CVSS score and how many of your hosts are affected. A finding like CVE-2026-116239 comes with the devices to patch.

    Learn more about EXYS7600 OCELOT
  • EXYS7950 KONDRA

    Detect it if it's exploited

    Until the patch is applied, Kondra monitors your network, events and endpoints in real time. It keeps an inventory of the software installed on every endpoint, and its anomaly detection rules flag what an attacker does once inside.

    Learn more about EXYS7950 KONDRA
Check your exposure

Assembled from the NVD 2.0 API, the CISA Known Exploited Vulnerabilities Catalog and FIRST EPSS. Scores are as of our last collection on 5 Nov 2026, not the live upstream state.