dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2025-12765

HIGH · 7.4 CVSS v3.1 Published 2025-11-13
Fix available
A fix is available. Upgrade to 9.10 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
pgAdmin <= 9.9  is affected by a vulnerability in the LDAP authentication mechanism allows bypassing TLS certificate verification.

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 · moderate confidence

pgAdmin versions 9.9 and earlier contain a vulnerability in the LDAP authentication module that allows bypassing TLS certificate verification. This enables man-in-the-middle attacks where an attacker could intercept LDAP authentication traffic by presenting a fraudulent certificate, potentially gaining unauthorized access to the pgAdmin instance.

MitigationUpgrade pgAdmin to a version newer than 9.9. Until the patch is applied, restrict network access to LDAP servers and consider using IPsec or VPN tunnels for LDAP traffic.

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
Affected:< 9.10

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check pgAdmin version
    Open the pgAdmin web interface and navigate to the 'About' page, or run 'pip show pgadmin4' from the command line to retrieve the installed package version
    Affected if The installed version is lower than 9.10 (for example, 9.9, 9.8, etc.)
  2. Verify LDAP authentication is enabled
    Examine the pgAdmin configuration files (config_local.py or config.py) for LDAP-related settings, or check the pgAdmin web interface under 'Settings' > 'Authentication' to see if LDAP is configured as an authentication source
    Affected if LDAP authentication is enabled and configured in pgAdmin
  3. Inspect LDAP TLS certificate verification settings
    Review the LDAP configuration parameters in the pgAdmin config file. Look for settings that control TLS/SSL certificate validation such as 'LDAP_CA_CERT_FILE', 'LDAP_TLS_CERT_ATTR', or similar options that govern whether TLS certificates are verified. Also check if 'LDAP_TLS_MODE' or equivalent is set to a mode that disables verification
    Affected if TLS certificate verification is explicitly disabled, or a configuration option allows bypassing certificate validation for LDAP connections

You are affected if pgAdmin version is below 9.10 AND LDAP authentication is configured with TLS certificate verification disabled or bypassed

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.10 or later
Fixed in 9.10
Interim mitigation

Upgrade pgAdmin to a version newer than 9.9. Until the patch is applied, restrict network access to LDAP servers and consider using IPsec or VPN tunnels for LDAP traffic.

Recommended fix High confidence

pgAdmin 4 version 9.10

  1. Verify current pgAdmin 4 version: pip show pgadmin4 or check the runtime About page
  2. Back up existing pgAdmin configuration and database (typically located at ~/.pgadmin or /var/lib/pgadmin)
  3. Upgrade pgAdmin 4 to version 9.10 or later using your installation method: pip install --upgrade pgadmin4==9.10
  4. If using Docker, pull the new image: docker pull dpage/pgadmin4:9.10
  5. Restart pgAdmin 4 service to load the updated version
  6. Verify the upgrade was successful and LDAP authentication is working as expected

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12765 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12765 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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