Quick answers
- Is CVE-2026-92868 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92868 being exploited in the wild.
- How severe is CVE-2026-92868?
- Medium severity, with a CVSS score of 6.5, published 30 September 2026.
- Which products and versions are affected?
- Pgpool Global Development Group Pgpool-II 4.0.x through 4.7.2.
- Is there a fix for CVE-2026-92868?
- A patch was published on 2026-09-29: Fixed in versions 4.7.3, 4.6.8, 4.5.13, 4.4.18, 4.3.21 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92868 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-92868?
- Check whether you run Pgpool Global Development Group Pgpool-II at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Pgpool-II improperly handles NUL bytes (\0) in the Common Name (CN) field of X.509 certificates during client authentication, allowing domain name validation to be bypassed. An unauthenticated attacker can craft a malicious certificate to authenticate as another user without providing credentials. The vulnerability affects versions 4.0.x through 4.7.2 and requires network access but no prior authentication.
Affected products
- Pgpool Global Development Group Pgpool-II 4.0.x through 4.7.2
Timeline
- 2026-09-29: disclosed
- 2026-09-29: patched: Fixed in versions 4.7.3, 4.6.8, 4.5.13, 4.4.18, 4.3.21