cve.bz

CVE-2026-92868 pgpool global development group pgpool-ii: Improper Certificate Validation

6.9 mediumEPSS 0.2%

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

On this page
An improper certificate validation vulnerability exists in Pgpool-II, which may allow an unauthenticated attacker to bypass client certificate authentication.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS 3.0

6.5 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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; 4th 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-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
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-92868 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92868?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92868?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-92868 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 4.0.x through 4.2.x

Linux distributions

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

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

Red Hat Product Security rates this vulnerability as Moderate severity because exploitation requires an environment specifically configured to authenticate users via client certificates, rather than standard password-based mechanisms. Within Red Hat ecosystems, Pgpool-II is not shipped in core Red Hat Enterprise Linux repositories and is maintained only in community Fedora channels. While bypassing certificate checks allows unauthorized network connections to reach the proxy, underlying backend database access controls still limit exposure.

Red Hat's mitigation

To mitigate this vulnerability, restrict network reachability to the Pgpool-II daemon using firewalld and configure password-based authentication instead of client certificate verification in pool_hba.conf.

1. Restrict incoming connections to the Pgpool-II port (default 9999) to trusted client addresses:

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

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

firewall-cmd --reload

2. In /etc/pgpool-II/pool_hba.conf, modify host authentication entries to require password authentication (such as scram-sha-256) instead of cert, and reload the daemon:

systemctl reload pgpool.service

Caveats:

Restricting access via firewall rules will block connection attempts from non-allowlisted client addresses. Transitioning authentication mechanisms away from client certificates requires modifying client application connection settings to supply credentials.

Warning:

Reloading firewall configurations or the Pgpool-II service will affect network connectivity and can interrupt active database sessions.

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

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON