# CVE-2026-92869: Memory corruption in Pgpool-II

> An authenticated attacker can trigger an out-of-bounds write in Pgpool-II, causing abnormal process termination and denial of service.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-92869, GHSA-r4r8-cv9q-rjpm

## What is CVE-2026-92869?

CVE-2026-92869 is a high-severity memory corruption 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

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

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-92869?


## How do I fix CVE-2026-92869?

Apply the vendor's patch.

## Is CVE-2026-92869 being exploited?

There is no known exploitation of CVE-2026-92869 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92869 and fix it if it is affected.

What it is: CVE-2026-92869 is a high-severity memory corruption 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-92869 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-92869/ (Markdown: https://insights.sbomify.com/CVE-2026-92869/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92869
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92869
- OSV: https://osv.dev/vulnerability/CVE-2026-92869

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92869/
Summaries are generated and may contain mistakes; the official description above is the record.