cve.bz

CVE-2026-92869 pgpool global development group pgpool-ii: Out-of-bounds Write

7.1 highEPSS 0.2%

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

On this page
An out-of-bounds write vulnerability exists in Pgpool-II, which may allow an authenticated attacker to cause abnormal process termination.

Severity

CVSS 4.0

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

CVSS 3.0

6.5 medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th 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: no · 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-787 Out-of-bounds Write
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-92869 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92869?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92869?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-92869 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-92869
Debian14pgpool24.7.3-1DEBIAN-CVE-2026-92869

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

Red Hat's statement

This vulnerability is rated as Moderate because exploitation requires authenticated network access and is strictly limited to causing a denial of service via process termination, without impacting confidentiality or system integrity. In typical Red Hat Enterprise Linux environments, Pgpool-II is not provided as a core component, substantially limiting exposure to community or specialized installations. The flaw cannot be triggered anonymously, meaning an attacker must possess valid database credentials to force the daemon to crash.

Red Hat's mitigation

Restrict network exposure by limiting access to the Pgpool-II service port to trusted hosts using firewall rules, or disable the service if Pgpool-II is not required.

1. Restrict incoming traffic to trusted IP addresses:

```

firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP>

firewall-cmd --permanent --remove-port=9999/tcp

firewall-cmd --reload

```

2. If connection pooling is not required, stop and disable the service:

```

systemctl stop pgpool

systemctl disable pgpool

```

Caveats:

Restricting access prevents unauthorized network endpoints from reaching the service. Stopping the service removes connection routing and pooling capabilities, requiring client applications to communicate directly with backend database servers.

Warning: Applying firewall reload rules or stopping the pgpool service terminates active client sessions and disrupts connection pooling availability.

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

References

Check your stackJSON