Pgpool Global Development Group Pgpool-II up to 4.7.2 certificate validation

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Pgpool Global Development Group Pgpool-II up to 4.7.2. This vulnerability affects unknown code. Performing a manipulation results in certificate validation. This vulnerability is cataloged as CVE-2026-92868. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Pgpool Global Development Group Pgpool-II up to 4.7.2. It has been classified as problematic. This affects an unknown functionality. The manipulation with an unknown input leads to a certificate validation vulnerability. CWE is classifying the issue as CWE-295. The product does not validate, or incorrectly validates, a certificate. This is going to have an impact on integrity. The summary by CVE is:

An improper certificate validation vulnerability exists in Pgpool-II, which may allow an unauthenticated attacker to bypass client certificate authentication.

The advisory is shared at pgpool.net. This vulnerability is uniquely identified as CVE-2026-92868 since 09/17/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/30/2026). MITRE ATT&CK project uses the attack technique T1587.003 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-89658). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Pgpool Global Development Group

Name

• Pgpool-II

Version

• 4.0
• 4.1
• 4.2
• 4.3.0
• 4.3.1
• 4.3.2
• 4.3.3
• 4.3.4
• 4.3.5
• 4.3.6
• 4.3.7
• 4.3.8
• 4.3.9
• 4.3.10
• 4.3.11
• 4.3.12
• 4.3.13
• 4.3.14
• 4.3.15
• 4.3.16
• 4.3.17
• 4.3.18
• 4.3.19
• 4.3.20
• 4.4.0
• 4.4.1
• 4.4.2
• 4.4.3
• 4.4.4
• 4.4.5
• 4.4.6
• 4.4.7
• 4.4.8
• 4.4.9
• 4.4.10
• 4.4.11
• 4.4.12
• 4.4.13
• 4.4.14
• 4.4.15
• 4.4.16
• 4.4.17
• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 4.5.7
• 4.5.8
• 4.5.9
• 4.5.10
• 4.5.11
• 4.5.12
• 4.6.0
• 4.6.1
• 4.6.2
• 4.6.3
• 4.6.4
• 4.6.5
• 4.6.6
• 4.6.7
• 4.7.0
• 4.7.1
• 4.7.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion