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.
CVE-2026-16529
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-30. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
August 21, 2026
Advisory Details (2)
Auto-updated Jul 30, 20262506032 – (CVE-2026-16529) CVE-2026-16529 PCP: PCP: Denial of Service due to signed integer overflow
https://bugzilla.redhat.com/show_bug.cgi?id=2506032Vendor Advisories for CVE-2026-16529(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | pcp-0:5.3.7-22.el8_10.5 | 2026-08-17 | redhat |
| redhat | pcp-0:7.0.3-5.el10_2 | 2026-08-17 | redhat |
| redhat | pcp-0:6.3.7-8.el9_8.4 | 2026-08-17 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pcp | 5.2.6-1 ... 7.2.0-1 (44 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pcp | 6.0.3-1.1 ... 7.2.1-2 (31 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pcp | 6.3.8-1 ... 7.2.1-2 (15 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pcp | 6.3.8-1 ... 7.2.0-1 (14 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(3)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 35× in last 7d / 148× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 226 total refreshes for this CVE.
- 2026-09-15 03:26 UTCEG score recompute
- 2026-09-15 03:26 UTCVendor advisory
- 2026-09-15 03:26 UTCGHSA enrichment
- 2026-09-14 14:49 UTCVendor advisory
- 2026-09-14 14:49 UTCGHSA enrichment
- 2026-09-14 01:20 UTCEG score recompute
- 2026-09-14 01:20 UTCVendor advisory
- 2026-09-14 01:20 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 13:43 UTCVendor advisory
- 2026-09-13 13:43 UTCGHSA enrichment
- 2026-09-13 02:06 UTCEG score recompute
- 2026-09-13 02:06 UTCVendor advisory
- 2026-09-13 02:06 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 14:28 UTCVendor advisory
- 2026-09-12 14:28 UTCGHSA enrichment
- 2026-09-12 02:50 UTCVendor advisory
- 2026-09-12 02:50 UTCGHSA enrichment
- 2026-09-11 15:12 UTCEG score recompute
- 2026-09-11 15:12 UTCVendor advisory
- 2026-09-11 15:12 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-11 03:31 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-11 03:31 UTCGHSA enrichment
- 2026-09-10 15:54 UTCEG score recompute
- 2026-09-10 15:54 UTCVendor advisory
- 2026-09-10 15:54 UTCGHSA enrichment
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-10 03:47 UTCVendor advisory
- 2026-09-10 03:47 UTCGHSA enrichment
- 2026-09-09 07:23 UTCEG score recompute
- 2026-09-09 07:23 UTCVendor advisory
- 2026-09-09 07:23 UTCGHSA enrichment
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 20:10 UTCEG score recompute
- 2026-09-07 20:10 UTCVendor advisory
- 2026-09-07 20:10 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 18:18 UTCEG score recompute
- 2026-09-06 18:18 UTCVendor advisory
- 2026-09-06 18:18 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 06:40 UTCVendor advisory
- 2026-09-06 06:40 UTCGHSA enrichment
- 2026-09-05 18:51 UTCEG score recompute
- 2026-09-05 18:51 UTCVendor advisory
- 2026-09-05 18:51 UTCGHSA enrichment
- 2026-09-05 04:59 UTCEG score recompute
- 2026-09-05 04:59 UTCVendor advisory
- 2026-09-05 04:59 UTCGHSA enrichment
- 2026-09-04 11:36 UTCEG score recompute
- 2026-09-04 11:36 UTCVendor advisory
- 2026-09-04 11:36 UTCGHSA enrichment
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 22:40 UTCEG score recompute
- 2026-09-01 22:40 UTCVendor advisory
- 2026-09-01 22:40 UTCGHSA enrichment
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 23:38 UTCVendor advisory
- 2026-08-31 23:38 UTCGHSA enrichment
- 2026-08-30 22:03 UTCEG score recompute
- 2026-08-30 22:03 UTCVendor advisory
- 2026-08-30 22:03 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 10:25 UTCEG score recompute
- 2026-08-30 10:25 UTCVendor advisory
- 2026-08-30 10:25 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:43 UTCEG score recompute
- 2026-08-29 22:43 UTCVendor advisory
- 2026-08-29 22:42 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 20:49 UTCEG score recompute
- 2026-08-27 20:49 UTCVendor advisory
- 2026-08-27 20:49 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 08:58 UTCVendor advisory
- 2026-08-27 08:58 UTCGHSA enrichment
- 2026-08-26 20:18 UTCEG score recompute
- 2026-08-26 20:18 UTCVendor advisory
- 2026-08-26 20:18 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 08:39 UTCVendor advisory
- 2026-08-26 08:39 UTCGHSA enrichment
- 2026-08-25 21:00 UTCEG score recompute
- 2026-08-25 21:00 UTCVendor advisory
- 2026-08-25 21:00 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 09:21 UTCVendor advisory
- 2026-08-25 09:21 UTCGHSA enrichment
- 2026-08-24 21:44 UTCEG score recompute
- 2026-08-24 21:44 UTCVendor advisory
- 2026-08-24 21:44 UTCGHSA enrichment
- 2026-08-24 10:06 UTCEG score recompute
- 2026-08-24 10:06 UTCVendor advisory
- 2026-08-24 10:06 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-16529?
When was CVE-2026-16529 disclosed?
Is CVE-2026-16529 actively exploited?
What is the CVSS score of CVE-2026-16529?
How do I remediate CVE-2026-16529?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-16529
Is Your Infrastructure Affected by CVE-2026-16529?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.