VulnerabilityPublished 13 Nov 2025

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, 09:15 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

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:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
pgadmin.org pgAdmin 4	Affected =0	Fixed in–

AI-suggested

1. Monitor pgAdmin.org and PostgreSQL security advisories closely for the release of official patches addressing CVE-2025-12765 and apply them promptly once available. 2. 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. 3. 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). 4. Implement network segmentation and use VPNs or secure tunnels for LDAP traffic to reduce exposure to MitM attacks. 5. Conduct regular security audits and penetration testing focusing on authentication mechanisms to detect potential misconfigurations or weaknesses. 6. Educate system administrators about the risks of this vulnerability and the importance of verifying TLS certificates in authentication flows. 7. 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.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of authentication credentials used in PostgreSQL database management. Many enterprises, government agencies, and critical infrastructure operators in Europe rely on pgAdmin 4 for database administration, often integrating LDAP for centralized authentication. A successful exploitation could allow attackers to intercept LDAP credentials, leading to unauthorized access to sensitive database systems. This could result in data breaches, exposure of personal or proprietary information, and potential compliance violations under regulations such as GDPR. Although the vulnerability does not directly affect data integrity or system availability, the compromise of authentication credentials can facilitate further lateral movement and privilege escalation within networks. The lack of required privileges or user interaction lowers the barrier for exploitation, increasing the urgency for mitigation. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as threat actors may develop exploits following public disclosure.

Summary

CVE-2025-12765 is a vulnerability identified in pgAdmin 4, a widely used open-source administration and management tool for PostgreSQL databases. The vulnerability exists in the LDAP authentication mechanism of pgAdmin versions up to 9.9, where the TLS certificate verification process can be bypassed. This flaw corresponds to CWE-295 (Improper Certificate Validation), meaning that pgAdmin fails to properly validate the authenticity of TLS certificates presented by LDAP servers during the authentication handshake. As a result, an attacker positioned as a man-in-the-middle (MitM) can intercept and manipulate LDAP authentication traffic without detection, potentially capturing sensitive credentials or session tokens. The CVSS v3.1 score of 7.5 (high severity) reflects the vulnerability's network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). The impact is primarily on confidentiality (C:H), with no direct impact on integrity (I:N) or availability (A:N). The vulnerability is exploitable remotely without authentication, increasing its risk profile. No patches were listed at the time of publication, and no known exploits have been reported in the wild, but the vulnerability's nature makes it a significant concern for organizations relying on LDAP for secure authentication in pgAdmin 4. The issue was reserved and published in November 2025, indicating recent discovery and disclosure.

CWE-295Improper Certificate Validation (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not validate, or incorrectly validates, a certificate.
Architecture and Design · Implementation
Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
Implementation
If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V9.2.1 (opens in a new tab)
V1.9.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/pgadmin-org/pgadmin4/issues/9324 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Nov 2025, 14:19 UTC

WeaknessesCWE-295

Technical details

References

Community reviews

Related threats