Quick answers
- Is CVE-2026-92871 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92871 being exploited in the wild.
- How severe is CVE-2026-92871?
- High severity, with a CVSS score of 7.5, published 30 September 2026.
- Which products and versions are affected?
- Pgpool Global Development Group Pgpool-II 3.5 through 4.7.2; fixed in 4.3.21, 4.4.18, 4.5.13, 4.6.8, 4.7.3.
- Is there a fix for CVE-2026-92871?
- A patch was published on 2026-09-29. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92871 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92871?
- 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
CVE-2026-92871 is a NULL pointer dereference (CWE-476) in Pgpool-II's watchdog inter-node authentication. When an authentication key is configured, malformed watchdog messages that omit authentication information trigger the defect, allowing unauthenticated attackers on the network to crash the watchdog process. A fix is available in patched versions.
Affected products
- Pgpool Global Development Group Pgpool-II 3.5 through 4.7.2; fixed in 4.3.21, 4.4.18, 4.5.13, 4.6.8, 4.7.3
Timeline
- 2026-09-29: disclosed
- 2026-09-29: patched