Is CVE-2026-92872 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92872 being exploited in the wild.

How severe is CVE-2026-92872?

Medium severity, with a CVSS score of 4.3, published 30 September 2026.

Which products and versions are affected?

Pgpool Global Development Group Pgpool-II versions 3.5.x through 4.7.2, specifically 4.7.0-4.7.2, 4.6.0-4.6.7, 4.5.0-4.5.12, 4.4.0-4.4.17, 4.3.0-4.3.20, and all versions from 3.5.x through 4.2.x.

Is there a fix for CVE-2026-92872?

A patch was published on 2026-09-29: Pgpool-II 4.7.3, 4.6.8, 4.5.13, 4.4.18, 4.3.21 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-92872 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-92872?

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.

CVE-2026-92872: Pgpool-II sensitive information insertion into log file

CVE-2026-92872 · Severity: medium · CVSS 4.3 · Published 2026-09-30

Pgpool-II is a middleware that pools PostgreSQL database connections for load balancing and high availability. An authenticated attacker can read cluster configuration details from log files, potentially exposing information about database infrastructure and topology that could be used in follow-up attacks.

Technologies: Pgpool Global Development Group Pgpool-II. Vendors: Pgpool Global Development Group.

Quick answers

Is CVE-2026-92872 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92872 being exploited in the wild.
How severe is CVE-2026-92872?: Medium severity, with a CVSS score of 4.3, published 30 September 2026.
Which products and versions are affected?: Pgpool Global Development Group Pgpool-II versions 3.5.x through 4.7.2, specifically 4.7.0-4.7.2, 4.6.0-4.6.7, 4.5.0-4.5.12, 4.4.0-4.4.17, 4.3.0-4.3.20, and all versions from 3.5.x through 4.2.x.
Is there a fix for CVE-2026-92872?: A patch was published on 2026-09-29: Pgpool-II 4.7.3, 4.6.8, 4.5.13, 4.4.18, 4.3.21 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-92872 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-92872?: 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

The heartbeat receiver process in Pgpool-II improperly inserts sensitive cluster information into log files (CWE-532), allowing an authenticated attacker with local log file access to disclosure configuration data. The vulnerability requires prior authentication to the system and affects the information disclosure impact, making exploitation dependent on local file access permissions.

Affected products

Pgpool Global Development Group Pgpool-II versions 3.5.x through 4.7.2, specifically 4.7.0-4.7.2, 4.6.0-4.6.7, 4.5.0-4.5.12, 4.4.0-4.4.17, 4.3.0-4.3.20, and all versions from 3.5.x through 4.2.x

Timeline

2026-09-29: disclosed
2026-09-29: patched: Pgpool-II 4.7.3, 4.6.8, 4.5.13, 4.4.18, 4.3.21 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.