VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

pcp: vulnerability history, versions and safety

pcp is a package in the Debian ecosystem. Vulert records 19 vulnerabilities for it across 44 releases, from Aug 2012 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
19 vulnerabilities recorded U19
i
9 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
6 in the last 12 months

Most recent disclosure 30 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pcp vulnerabilities

Vulert verdict on pcp i

Updated on 23 Oct 2026

Careful: 9 of the 19 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 19 vulnerabilities on record across 13 years, 6 in the last year.

What to do: Plan around the 9 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 19 over 13 years · 6 in the last year i
  • Latest disclosure 30 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 9 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for pcp, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 44 of 44 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 10
  • 2024 3
  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 19 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for pcp

The 5 most severe of 19 vulnerabilities recorded for this package

Search all 19 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Privilege Escalation Vulnerability in PCP Package: CVE-2026-16526 8.8 high No fix published 30 Jul 2026
Command Injection Vulnerability in PCP Package: CVE-2026-16524 7.8 high No fix published 30 Jul 2026
Integer Overflow Vulnerability in PCP Package Leading to Denial of Service 7.5 high No fix published 30 Jul 2026
Critical Access Control Bypass in PCP Package Leading to Remote Code Execution 7.3 high No fix published 30 Jul 2026
Privilege Escalation Vulnerability in Performance Co-Pilot (PCP) 6.7 medium No fix published 28 Feb 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About pcp

Is pcp safe to use?

Vulert records 19 vulnerabilities for pcp in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 19 not yet rated. 9 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does pcp have?

19 vulnerabilities are recorded for pcp in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 19 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pcp vulnerabilities disclosed?

6 vulnerabilities were recorded for pcp in the last 12 months, and the oldest entry in this database dates to 27 Aug 2012. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of pcp are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor pcp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pcp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.