cve.bz

CVE-2026-92870 pgpool global development group pgpool-ii: Stack-based Buffer Overflow

8.7 highEPSS 0.3%

High (8.7) in pgpool global development group pgpool-ii. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A stack-based buffer overflow vulnerability exists in Pgpool-II, which may allow an unauthenticated attacker to cause abnormal process termination.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.0

7.5 high
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-92870 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92870?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92870?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-92870 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.

Affected

  • pgpool global development group:pgpool-ii

Versions

From the CNA's record in the CVE List.

ProductAffected
Pgpool Global Development Group Pgpool-IIfrom 4.7.0 through 4.7.2
Pgpool Global Development Group Pgpool-IIfrom 4.6.0 through 4.6.7
Pgpool Global Development Group Pgpool-IIfrom 4.5.0 through 4.5.12
Pgpool Global Development Group Pgpool-IIfrom 4.4.0 through 4.4.17
Pgpool Global Development Group Pgpool-IIfrom 4.3.0 through 4.3.20
Pgpool Global Development Group Pgpool-IIfrom 3.5.x through 4.2.x

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13pgpool2no fix listedDEBIAN-CVE-2026-92870
Debian14pgpool24.7.3-1DEBIAN-CVE-2026-92870

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

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important severity because it enables remote, unauthenticated attackers to abruptly terminate the service without prior credentials, elevating the risk beyond Moderate due to the immediate outage imposed on all dependent database operations. Pgpool-II acts as a connection pooler and proxy for PostgreSQL environments; crashing the daemon severs active connections and halts transactional processing. This component is not distributed in Red Hat Enterprise Linux and is only packaged through community channels such as Fedora.

Red Hat's mitigation

Restrict network reachability to the Pgpool-II listening port (by default TCP port 9999) using firewalld so that only trusted client application hosts can initiate connections.

To limit access to a trusted source subnet using firewalld rich rules, run:

firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.0.2.0/24" port port="9999" protocol="tcp" accept'

firewall-cmd --reload

If the Pgpool-II service is not required on the system, stop and disable it:

systemctl stop pgpool

systemctl disable pgpool

Caveats: Restricting incoming traffic blocks untrusted network hosts from reaching the proxy. Stopping the daemon prevents client connections from being pooled or routed to PostgreSQL backend servers. Warning: Reloading firewall rules or stopping the service will disrupt active client connections and cause transient connectivity outages.

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-92870.

References

Check your stackJSON