CVE-2026-92872: Pgpool-II · Sensitive Data in Logs
Affects Pgpool-IISource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 12 Nov 2026, 23:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Pgpool Global Development GroupPgpool-II | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict access to log files to authorized users only to prevent unauthorized reading of sensitive information.
Description
Pgpool-II inserts sensitive information into log file, which may allow an authenticated attacker to obtain the cluster information.