CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NHigh (8.7) in pgpool global development group pgpool-ii. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-92871 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92871?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92871?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92871 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Pgpool Global Development Group Pgpool-II | from 4.7.0 through 4.7.2 |
| Pgpool Global Development Group Pgpool-II | from 4.6.0 through 4.6.7 |
| Pgpool Global Development Group Pgpool-II | from 4.5.0 through 4.5.12 |
| Pgpool Global Development Group Pgpool-II | from 4.4.0 through 4.4.17 |
| Pgpool Global Development Group Pgpool-II | from 4.3.0 through 4.3.20 |
| Pgpool Global Development Group Pgpool-II | from 3.5.x through 4.2.x |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | pgpool2 | no fix listed | DEBIAN-CVE-2026-92871 |
| Debian | 14 | pgpool2 | 4.7.3-1 | DEBIAN-CVE-2026-92871 |
From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.
Red Hat rates this Important.
This vulnerability is rated as Important because an unauthenticated remote attacker can crash the watchdog daemon over the network, causing a denial of service and disrupting cluster high-availability coordination. Standalone deployments where the watchdog subsystem is disabled are not exposed to this issue. In clustered configurations, exposure is limited when watchdog communication ports are restricted to private, trusted cluster networks in accordance with standard deployment practices.
Restrict network access to the pgpool-II watchdog service to trusted cluster nodes using firewall rules, or disable the watchdog process if high-availability clustering is not required:
1. Limit watchdog communication ports (default TCP port 9000 and heartbeat port 9694) to authorized cluster peers using firewalld:
```
# firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<TRUSTED_NODE_IP>" port port="9000" protocol="tcp" accept'
# firewall-cmd --permanent --add-rich-rule='rule family="ipv4" port port="9000" protocol="tcp" drop'
# firewall-cmd --reload
```
2. Alternatively, if watchdog clustering is not utilized, disable it in `/etc/pgpool-II/pgpool.conf`:
```
use_watchdog = off
```
Apply the configuration change by restarting the service:
```
# systemctl restart pgpool.service
```
Caveats:
Disabling watchdog removes automated node failover and split-brain detection among pgpool-II instances. Restricting port access via firewall requires adding rich rules for each authorized cluster member.
Warning: Restarting or reloading the pgpool service interrupts active database connections and causes temporary downtime.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-92871.