CVE-2025-12765: pgAdmin 4 · CWE-295
Affects pgAdmin 4Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pgadmin.org pgAdmin 4 | Affected
| Fixed in– |
AI-suggested
- Monitor pgAdmin.org and PostgreSQL security advisories closely for the release of official patches addressing CVE-2025-12765 and apply them promptly once available.
- Until patches are released, consider disabling LDAP authentication in pgAdmin 4 or replacing it with alternative, more secure authentication methods such as certificate-based or Kerberos authentication.
- Enforce strict TLS certificate validation policies at the network level, including the use of LDAP servers with properly signed certificates from trusted Certificate Authorities (CAs).
- Implement network segmentation and use VPNs or secure tunnels for LDAP traffic to reduce exposure to MitM attacks.
- Conduct regular security audits and penetration testing focusing on authentication mechanisms to detect potential misconfigurations or weaknesses.
- Educate system administrators about the risks of this vulnerability and the importance of verifying TLS certificates in authentication flows.
- Employ intrusion detection systems (IDS) and network monitoring tools to detect unusual LDAP traffic patterns that may indicate exploitation attempts.
Description
CVE-2025-12765 is a high-severity vulnerability affecting pgAdmin 4 versions up to 9.9, specifically in its LDAP authentication mechanism. The flaw allows an attacker to bypass TLS certificate verification, enabling potential man-in-the-middle attacks during LDAP authentication. This vulnerability does not require authentication or user interaction and can be exploited remotely over the network. While it impacts confidentiality by potentially exposing sensitive authentication credentials, it does not affect integrity or availability. No known exploits are currently reported in the wild. European organizations using pgAdmin 4 with LDAP authentication are at risk, especially those in countries with significant PostgreSQL adoption and critical infrastructure relying on secure database management. Mitigation involves applying patches once available, enforcing strict TLS validation policies, and considering alternative authentication methods until patched. Countries like Germany, France, the UK, the Netherlands, and Sweden are likely most affected due to their extensive use of PostgreSQL and related tools in enterprise and government sectors.