Is CVE-2026-116238 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-116238 being exploited in the wild.

How severe is CVE-2026-116238?

High severity, with a CVSS score of 8.1, published 30 October 2026.

Is there a fix for CVE-2026-116238?

Yes: fixed in pgAdmin 4 9.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-116238 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-116238?

Check whether you run Pgadmin 4 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-116238: pgAdmin 4 account lockout bypass and unlimited password guessing

CVE-2026-116238 · Severity: high · CVSS 8.1 · Published 2026-10-30

pgAdmin 4, a web-based database management tool, implements login attempt limiting to lock accounts after repeated failed password guesses. In server mode, multiple weaknesses allow an attacker to bypass these protections and make unlimited password guessing attempts against administrator and internal accounts. This could lead to unauthorized access and complete compromise of the database management interface.

Technologies: Pgadmin 4. Vendors: pgAdmin.

Quick answers

Is CVE-2026-116238 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116238 being exploited in the wild.
How severe is CVE-2026-116238?: High severity, with a CVSS score of 8.1, published 30 October 2026.
Which products and versions are affected?: Pgadmin 4 before 9.19.
Is there a fix for CVE-2026-116238?: Yes: fixed in pgAdmin 4 9.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116238 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-116238?: Check whether you run Pgadmin 4 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: pgAdmin 4 9.19

Technical details

The vulnerability involves multiple authentication bypass vectors in pgAdmin 4's server mode: Flask-Security views bypass pgAdmin's failed login counting and account locking; username matching ignores case while the lock mechanism does not; LDAP/webserver/Kerberos authentication fallbacks prevent password attempt counting; and password reset and account information disclosure are not properly restricted. An unauthenticated attacker can exploit these flaws to conduct unlimited brute-force password attacks against internal accounts, including administrators, in the default configuration.

Affected products

pgAdmin pgAdmin 4 before 9.19

Timeline

2026-10-30: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.