Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.18% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-92872High confidence
Pgpool-II inserts sensitive information into log file, which may allow an authenticated attacker to obtain the cluster information
Pgpool Global Development Group · Pgpool-II
5.3MediumCVSS 4.0
Scheduled
Fix not verifiedMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Pgpool Global Development Group Pgpool-II and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | pgpool2 | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian bookwormbookworm · source | pgpool2 | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian forkyforky · source | pgpool2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 4.7.3-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian sidsid · source | pgpool2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 4.7.3-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-92872 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypgpool-II: pgpool-II: Information disclosure via log files
The vendor explicitly states that these products are not affected by this CVE.
- All currently supported Red Hat products
- Summary
- A flaw was found in Pgpool-II. The application writes sensitive cluster details directly into log files. An authenticated attacker can exploit this issue to view database cluster information, resulting in unauthorized information disclosure.
- Remediation
- No remediation text is recorded.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verified01
What, why and how
Pgpool-II inserts sensitive information into log file, which may allow an authenticated attacker to obtain the cluster information.
What
Pgpool-II inserts sensitive information into log file, which may allow an authenticated attacker to obtain the cluster information.
Why
The product writes sensitive information to a log file.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.
What
Pgpool-II inserts sensitive information into log file, which may allow an authenticated attacker to obtain the cluster information.
Why
The product writes sensitive information to a log file.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Insertion of Sensitive Information into Log File → obtain information outside the intended access boundary
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-532 ↗
CWE-532: Insertion of Sensitive Information into Log File. The product writes sensitive information to a log file.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCLowVulnerable-system confidentiality: A successful attack can cause a limited loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- Pgpool-II: 4.7.0 ≤ 4.7.2, 4.6.0 ≤ 4.6.7, 4.5.0 ≤ 4.5.12, 4.4.0 ≤ 4.4.17, 4.3.0 ≤ 4.3.20, 3.5.x ≤ 4.2.x
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 30 Sept 2026 · Last source change 30 Sept 2026, 16:59 UTC · CWE-532 · Insertion of Sensitive Information into Log File
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-30
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-89676
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2026-89676 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-89676"}
- Vendor guidanceAuthoritative vendor guidance changed: removed mitigation: jvndb.jvn.jp/JVNDB-2026-000140.html; removed remediation: jvndb.jvn.jp/JVNDB-2026-000140.html.CNA ↗
- Before
- mitigation: jvndb.jvn.jp/JVNDB-2026-000140.html · remediation: jvndb.jvn.jp/JVNDB-2026-000140.html
- After
- no authoritative guidance recorded
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- PgPool Global Development Group / Pgpool-II: 3.5系から4.2系までのすべてのバージョン(CVE-2026-92867、CVE-2026-92869、CVE-2026-92870、CVE-2026-92871、CVE-2026-92872、CVE-2026-92873)、4.0系から4.2系までのすべてのバージョン(CVE-2026-92868)、バージョン 4.3.0から4.3.20まで(CVE-2026-92867、CVE-2026-92868、CVE-2026-92869、CVE-2026-92870、CVE-2026-92871、CVE-2026-92872、CVE-2026-92873)、バージョン 4.4.0から4.4.17まで(CVE-2026-92867、CVE-2026-92868、CVE-2026-92869、CVE-2026-92870、CVE-2026-92871、CVE-2026-92872、CVE-2026-92873)、バージョン 4.5.0から4.5.12まで(CVE-2026-92867、CVE-2026-92868、CVE-2026-92869、CVE-2026-92870、CVE-2026-92871、CVE-2026-92872、CVE-2026-92873)、バージョン 4.6.0から4.6.7まで(CVE-2026-92867、CVE-2026-92868、CVE-2026-92869、CVE-2026-92870、CVE-2026-92871、CVE-2026-92872、CVE-2026-92873)、バージョン 4.7.0から4.7.2まで(CVE-2026-92867、CVE-2026-92868、CVE-2026-92869、CVE-2026-92870、CVE-2026-92871、CVE-2026-92872、CVE-2026-92873) · Fixed: The authority publishes remediation guidance. Confirm the exact fixed release in the linked primary advisory.
- After
- Pgpool-II: 4.7.0 ≤ 4.7.2, 4.6.0 ≤ 4.6.7, 4.5.0 ≤ 4.5.12, 4.4.0 ≤ 4.4.17, 4.3.0 ≤ 4.3.20, 3.5.x ≤ 4.2.x · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Patch available to Awaiting fix.CNA ↗
- Before
- Patch available
- After
- Awaiting fix
- SeveritySeverity changed from High to Medium.CNA ↗
- Before
- High
- After
- Medium
- CVSS scoreCVSS score changed from 8.8 (CVSS 3.0 · Other authority · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) to 5.3 (CVSS 4.0 · CNA · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N).CNA ↗
- Before
- 8.8 (CVSS 3.0 · Other authority · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
- After
- 5.3 (CVSS 4.0 · CNA · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N)
- Catalogue recordCVE added to the BlackTree catalogue.Official national cybersecurity authority ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.