# CVE-2026-16529: Pcp: pcp: denial of service due to signed integer overflow

> A signed integer overflow in PCP allows remote attackers to cause a permanent denial of service via crafted network packets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2026
- **Updated:** 1 Oct 2026
- **Also known as:** AZL-94374, DEBIAN-CVE-2026-16529, GHSA-hm96-wjh8-qqgm, UBUNTU-CVE-2026-16529

## What is CVE-2026-16529?

CVE-2026-16529 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A signed integer overflow in the PCP __pmGetPDU() function can be exploited via crafted network packets during PDU processing or SASL negotiation. This permanently blinds the affected daemon, resulting in a total denial of service (DoS) for subsequent packet reads.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-16529 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16529 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16529 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-16529/ (Markdown: https://insights.sbomify.com/CVE-2026-16529/index.md)
```

## Sources

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

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