Pgadmin 4Application · Pgadmin
CVE-2025-12764
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedpgAdmin <= 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencepgAdmin versions 9.9 and below contain an LDAP injection vulnerability in the LDAP authentication module. Attackers can inject special LDAP characters (such as wildcards or filter operators) into the username field during authentication. This causes the LDAP directory server to process excessively complex or large queries, resulting in denial of service for both the LDAP server and the pgAdmin client.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Pgadmin 4Application
< 9.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed pgAdmin 4 versionLocate the pgAdmin 4 version number in the application (Help menu > About) or query the Python package if deployed as a pip installationAffected if The installed version is 9.9 or lower (any version below 9.10)
-
Identify LDAP authentication method in useExamine pgAdmin configuration files or runtime settings for LDAP authentication configuration parameters (e.g., LDAP_SERVER, LDAP_PORT, LDAP_BASE_DN, or similar LDAP-related settings)Affected if LDAP is configured as an authentication source; if local password or other non-LDAP auth is used, this vulnerability does not apply
-
Verify LDAP username handling behaviorInspect the LDAP authentication module code or logs to confirm whether username input is passed directly into LDAP filter construction without sanitization of special charactersAffected if Usernames are used directly in LDAP search filters without filtering out metacharacters such as *, (, ), \, or NUL characters
A user is affected if pgAdmin 4 version is below 9.10 AND LDAP authentication is enabled, allowing unvalidated LDAP metacharacters in usernames to reach the directory server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.10
Upgrade pgAdmin to a version beyond 9.9. Additionally, implement input validation to sanitize or reject special LDAP metacharacters (e.g., *, (, ), \, NUL) in usernames before constructing LDAP search filters.
pgAdmin 4 version 9.10
- Upgrade pgAdmin 4 to version 9.10 or later
- Verify the upgrade completed successfully
- Test LDAP authentication to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pgadmin 4
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12764 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12764 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data