Skip to content

GHSA-cvf4-f829-762v CVE-2025-12764 PYSEC-2026-1772

pgAdmin is affected by an LDAP injection vulnerability

High PyPI
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.48%
Chance of exploitation in the next 30 days. Higher than 41.11% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-90 Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')
Fix
9.10
Upgrade pgadmin4 to this version or later

Description

pgAdmin <= 9.9 is affected by an LDAP injection vulnerability in the LDAP authentication flow that allows an attacker to inject special LDAP characters in the username, causing the DC/LDAP server and the client to process an unusual amount of data DOS.

Affected versions

PyPI

PackageVulnerableFixed in
pgadmin4
< 9.10
9.10

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

pgadmin4 PyPI → 9.10

pip
pip install --upgrade "pgadmin4>=9.10"
poetry
poetry add "pgadmin4>=9.10"
uv
uv add "pgadmin4>=9.10"

Severity breakdown

CVSS 3.1 7.5

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-90: Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')

The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.

How to prevent it
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-hv9p-2pqf-r5w3
pgAdmin 4: Improper restriction of excessive authentication attempts
Medium Also affects pgadmin4
GHSA-hr4r-fwpv-c95j
pgAdmin 4 File Manager has symbolic-link path traversal
High Also affects pgadmin4
GHSA-4rhg-h8f2-v4jm
pgAdmin 4 has deserialization of untrusted data in its FileBackedSessionManager
High Also affects pgadmin4
GHSA-p58c-q354-6c4f
pgAdmin 4 contains local file inclusion (LFI) and server-side request forgery (SSRF) vulnerabilities
Medium Also affects pgadmin4
GHSA-j74f-g7vx-fh4x
pgAdmin 4: OS command injection vulnerability in Import/Export query export
High Also affects pgadmin4
GHSA-hp84-p2gq-6fvr
SQL injection vulnerability in pgAdmin 4 Maintenance Tool
High Also affects pgadmin4
GHSA-6p2c-69cv-3fxq
pgAdmin 4: Stored cross-site scripting (XSS) vulnerability in Browser Tree and Explain Visualizer modules
Medium Also affects pgadmin4
GHSA-h2x2-q2mc-24gw
pgAdmin 4 server mode has an authorization vulnerability affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules
Critical Also affects pgadmin4
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor