Out-of-Bounds Read in PCP (Performance Co-Pilot) pmproxy service (CVE-2026-16530)
Summary
Vulnerability in PCP (Performance Co-Pilot) pmproxy service (CVE-2026-16530). Risk of unauthorized operations or information disclosure. Exploitable via pmproxy.
Original description
The description as published by the source.
A flaw was found in the PCP (Performance Co-Pilot) pmproxy service. A remote attacker can exploit a vulnerability in the pmLogLoadInDom() function by sending a specially crafted request. This bypasses a critical bounds check, which can lead to the pmproxy service crashing, causing a Denial of Service (DoS). Additionally, this flaw may enable the leakage of sensitive information from the system's memory.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-16530 has been found in PCP (Performance Co-Pilot) pmproxy service.
Attackers can target a specific entry point like pmproxy over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "PCP (Performance Co-Pilot) pmproxy service CVE-2026-16530" on the vendor's site.
CVE-2026-16530 (PCP (Performance Co-Pilot) pmproxy service) — CWE-125 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: pmproxy
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Out-of-bounds read (CWE-125) exists in PCP (Performance Co-Pilot) pmproxy service. Attackers reach the vulnerable code path via pmproxy without authentication.
Check the vendor advisory for the affected versions of PCP (Performance Co-Pilot) pmproxy service. Attack surface: pmproxy.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで PCP (Performance Co-Pilot) pmproxy service を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-16530 pcp
- Ubuntu UBUNTU-CVE-2026-16530 pcp
References
- web nvd.nist.gov
- web secalert@redhat.com
- web secalert@redhat.com
- web github.com