CVE-2026-92868Network attack vectorHinoki check available

User impersonation via NUL-truncated certificate common name

Published Sep 30, 2026 · Updated Sep 30, 2026

Improper certificate validation in Pgpool-II 4.0 through 4.7.2 allows remote attackers to assume another database user via a crafted client certificate. Client certificate authentication compares the certificate common name with the requested username but treats an embedded NUL byte as a valid match despite a different complete name. Exploitation requires an SSL connection using certificate authentication and a valid client certificate; the bypass removes the need for the impersonated user's password.

CVSS severity6.9
Medium
EPSS probability0.15%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Improper certificate validation in Pgpool-II 4.0 through 4.7.2 allows remote attackers to assume another database user via a crafted client certificate. Client certificate authentication compares the certificate common name with the requested username but treats an embedded NUL byte as a valid match despite a different complete name. Exploitation requires an SSL connection using certificate authentication and a valid client certificate; the bypass removes the need for the impersonated user's password.

The record

CVE
CVE-2026-92868
Published
Sep 30, 2026
Updated
Sep 30, 2026
Vendor
Pgpool Global Development Group
Product
Pgpool-II
Classifications
CWE-295, T1649
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 30, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 30, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.0.x <=4.2.x
  2. Affected versionversion=4.3.0 <=4.3.20
  3. Affected versionversion=4.4.0 <=4.4.17
  4. Affected versionversion=4.5.0 <=4.5.12
  5. Affected versionversion=4.6.0 <=4.6.7
  6. Affected versionversion=4.7.0 <=4.7.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Pgpool Global Development Group · Pgpool-IIversion=4.0.x <=4.2.x; version=4.3.0 <=4.3.20; version=4.4.0 <=4.4.17; version=4.5.0 <=4.5.12; version=4.6.0 <=4.6.7; version=4.7.0 <=4.7.2

Published CVSS scores

6.5JPCERT/CC and IPACVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
6.9JPCERT/CC and IPACVSS: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 describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-295Improper Certificate Validation
T1649Steal or Forge Authentication Certificates

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started