Critical Security Flaws in Performance Co-Pilot (PCP) Packages: Command Injection and Privilege Escalation

pcp-conf Updated 19 Aug 2026

Summary

17/08/2026
N/A
Yes i
Unrated
Not published

ALSA-2026:55560: Important: pcp security update. Affects pcp-conf versions < 5.3.7-22.el8_10.5. Fixed in 5.3.7-22.el8_10.5. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Performance Co-Pilot (PCP) is a suite of tools, services, and libraries designed for the acquisition, archiving, and analysis of system-level performance measurements. Its lightweight distributed architecture makes it particularly effective for centralized analysis of complex systems. However, recent vulnerabilities have raised concerns about its security, particularly regarding the linux_sockets PMDA and pmproxy components.

Vulnerability Detail

The vulnerabilities identified in PCP include arbitrary command execution via command injection (CVE-2026-16524), privilege escalation to root through the linux_sockets PMDA (CVE-2026-16526), unauthenticated access to the /store endpoint allowing bypassing pmcd access rules (CVE-2026-16527), and denial of service due to signed integer overflow (CVE-2026-16529). These vulnerabilities can lead to severe security breaches, allowing attackers to execute arbitrary commands, gain unauthorized access, or disrupt service availability.

How To Fix

Minimum fixed version

5.3.7-22.el8_10.5

This is the first release that contains the fix.

sudo dnf update pcp-conf

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, you can restrict access to the /store endpoint and limit the use of the linux_sockets PMDA until the packages are updated. Additionally, consider implementing network security measures to mitigate the risk of unauthorized access.

Conclusion

The vulnerabilities in Performance Co-Pilot (PCP) pose significant security risks, including command injection and privilege escalation. It is crucial to update the affected packages to the latest patched version to safeguard your systems. Additionally, utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for pcp-conf →

Share this vulnerability

FAQ

The vulnerabilities include command injection, privilege escalation, unauthenticated access, and denial of service.

You can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software using a manifest file like package-lock.json. Visit Vulert Scanner to check your application without signup.

Consequences include unauthorized command execution, privilege escalation to root, and service disruption, which can severely impact system security and availability.

Yes, a patch is available in version 5.3.7-22.el8_10.5. Updating to this version will resolve the vulnerabilities.

Implement access restrictions to vulnerable components and enhance network security to mitigate risks until you can apply the updates.

How To Fix

Minimum fixed version

5.3.7-22.el8_10.5

This is the first release that contains the fix.

sudo dnf update pcp-conf

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback