Red Hat Updates Performance Co-Pilot on RHEL 8 for Four Vulnerabilities
Tech GuruQuick Answer
Update affected Performance Co-Pilot packages on the listed RHEL 8.4 or 8.6 support branches. RHSA-2026:74613 supplies the 8.4 build 5.2.5-8.el8_4.1; 74612 supplies the 8.6 build 5.3.5-10.el8_6.1. These records cover Advanced Mission Critical Update Support and Extended Update Support Long-Life Add-On, not every RHEL 8 installation.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Performance Co-Pilot packages for RHEL 8.4 and 8.6 AUS/EUS Extension branches, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-10-02 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Performance Co-Pilot packages for RHEL 8.4 and 8.6 AUS/EUS Extension branches |
|---|---|
| Advisory | RHSA-2026:74612 / RHSA-2026:74613 |
| CVEs | CVE-2026-16524, CVE-2026-16526, CVE-2026-16527, CVE-2026-16529 |
| Authoritative release date | 2026-10-01 23:12:25 UTC |
| Authority revision date | Latest current_release_date in the checked advisory set: 2026-10-02T04:51:06+00:00. Individual advisories may have earlier revisions. |
| Affected versions | Advisory-listed pcp builds before the fixed 8.4 and 8.6 source packages. |
| Fixed version | pcp 5.2.5-8.el8_4.1 / pcp 5.3.5-10.el8_6.1 |
| CVSS base score | 7.3–8.8 (official CVSS v3.1 range) |
| CVSS severity | High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Two findings concern linux_sockets PMDA command execution and privilege escalation; another lets pmproxy /store requests bypass pmcd access rules; the fourth is an integer-overflow denial of service. The privilege-escalation condition differs between DSO and default daemon mode, so record how the agent is actually loaded. pmcd rules alone do not establish protection of the pmproxy path.
What To Validate Now
- Inventory. Locate Performance Co-Pilot packages for RHEL 8.4 and 8.6 AUS/EUS Extension branches deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Match entitlement, product stream, architecture, source package or image repository, and each advisory's product status. Do not apply one branch's build or digest to another branch.
- Remediate. Use the entitled 8.4 or 8.6 repository and update affected installed PCP binaries from the matching build. Review pmproxy exposure and linux_sockets loading mode with the monitoring owner while arranging the update. Do not apply another minor release's package or disable collection without assessing monitoring loss.
- Validate. Confirm installed PCP builds and required service restarts, then check metric collection, archive continuity and dashboard queries. Review pmcd access rules and pmproxy reachability separately. Use approved read-only queries; do not execute a command-injection payload or write performance-control values as a test.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Restrict monitoring endpoints to required trusted clients. Temporary restrictions may interrupt collection, so record the resulting monitoring gap and restore only approved access. Preserve archives and configuration before changes; this notice has not tested PCP service or dashboard behavior.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
