CVE-2026-92872 Information disclosure in Pgpool-II
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-92872 and fix it if it is affected.
What it is: CVE-2026-92872 is a medium-severity vulnerability in Pgpool-II, published on 30 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92872 in the wild and no public exploit code.
Affected product: Pgpool-II. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-92872/ (Markdown: https://insights.sbomify.com/CVE-2026-92872/index.md)
An authenticated attacker can obtain sensitive cluster information from Pgpool-II log files, potentially aiding further attacks.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-92872?
CVE-2026-92872 is a medium-severity vulnerability in Pgpool-II, published on 30 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Pgpool-II inserts sensitive information into log file, which may allow an authenticated attacker to obtain the cluster information.
Weakness: CWE-532
Which versions are affected by CVE-2026-92872?
How do I fix CVE-2026-92872?
Apply the vendor's patch.
Is CVE-2026-92872 being exploited?
There is no known exploitation of CVE-2026-92872 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2026-92872, GHSA-84mj-xfmv-f82h.