CVE-2026-16527

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-30. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An unauthenticated remote attacker can bypass access controls by sending crafted requests to the PCP pmproxy /store endpoint. This allows the attacker to overwrite any PMDA metric, leading to arbitrary code execution and system takeover.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
48
EG Risk 48/100

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 computed (value × EchelonGraph’s weight)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 30, 2026

Last Modified

October 2, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
Patch available. Sources: redhat.
Red Hat

2506031 – (CVE-2026-16527) CVE-2026-16527 PCP: PCP pmproxy: Unauthenticated access to /store endpoint allows bypassing pmcd access rules

https://bugzilla.redhat.com/show_bug.cgi?id=2506031
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-16527

Vendor Advisories for CVE-2026-16527(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpcp-0:5.2.5-8.el8_4.12026-10-01redhat
redhatpcp-0:5.3.5-10.el8_6.12026-10-01redhat
redhatpcp-0:5.3.7-19.el8_8.12026-09-30redhat
redhatpcp-0:6.2.0-5.el9_4.22026-09-28redhat
redhatpcp-0:6.3.7-1.el10_0.12026-09-28redhat
redhatpcp-0:6.3.7-1.el9_6.12026-09-28redhat
redhatpcp-0:6.0.1-8.el9_2.22026-09-28redhat
redhatpcp-0:6.3.7-8.el9_8.42026-08-17redhat
redhatpcp-0:5.3.7-22.el8_10.52026-08-17redhat
redhatpcp-0:7.0.3-5.el10_22026-08-17redhat

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)
PackageVulnerable rangeFix by version rangeDependents
pcp5.2.6-1 ... 7.2.0-1 (44 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pcp6.0.3-1.1 ... 7.2.1-2 (31 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pcp6.3.8-1 ... 7.2.1-2 (15 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pcp6.3.8-1 ... 7.2.0-1 (14 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 107× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 327 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 227 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-10-12 16:30 UTCEG score recompute
  5. 2026-10-11 20:09 UTCEG score recompute
  6. 2026-10-11 17:21 UTCEG score recompute
  7. 2026-10-11 14:54 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-06 23:55 UTCEG score recompute
  14. 2026-10-06 23:55 UTCVendor advisory
  15. 2026-10-06 23:55 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  16. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-10-05 20:07 UTCEG score recompute
  18. 2026-10-05 20:07 UTCVendor advisory
  19. 2026-10-05 20:06 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  20. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  21. 2026-10-04 23:59 UTCEG score recompute
  22. 2026-10-04 23:59 UTCVendor advisory
  23. 2026-10-04 23:59 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  24. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-10-04 06:44 UTCEG score recompute
Show 75 more
  1. 2026-10-04 06:44 UTCVendor advisory
  2. 2026-10-04 06:44 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  3. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-10-02 17:02 UTCEG score recompute
  5. 2026-10-02 17:02 UTCVendor advisory
  6. 2026-10-02 17:02 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  7. 2026-10-02 00:25 UTCEG score recompute
  8. 2026-10-02 00:25 UTCVendor advisory
  9. 2026-10-02 00:25 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  10. 2026-10-02 00:01 UTCEG score recompute
  11. 2026-10-02 00:01 UTCVendor advisory
  12. 2026-10-02 00:00 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-01 12:11 UTCVendor advisory
  15. 2026-10-01 12:11 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  16. 2026-09-30 23:33 UTCEG score recompute
  17. 2026-09-30 23:33 UTCVendor advisory
  18. 2026-09-30 23:33 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  19. 2026-09-30 23:02 UTCEG score recompute
  20. 2026-09-30 23:02 UTCVendor advisory
  21. 2026-09-30 23:02 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  22. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-09-28 22:29 UTCEG score recompute
  25. 2026-09-28 22:29 UTCVendor advisory
  26. 2026-09-28 22:29 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  27. 2026-09-28 22:13 UTCEG score recompute
  28. 2026-09-28 22:13 UTCVendor advisory
  29. 2026-09-28 22:13 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  30. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-09-28 10:38 UTCEG score recompute
  32. 2026-09-28 10:38 UTCVendor advisory
  33. 2026-09-28 10:38 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  34. 2026-09-28 09:42 UTCEG score recompute
  35. 2026-09-28 09:42 UTCVendor advisory
  36. 2026-09-28 09:42 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  37. 2026-09-28 07:38 UTCVendor advisory
  38. 2026-09-28 07:38 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  39. 2026-09-27 19:06 UTCEG score recompute
  40. 2026-09-27 19:06 UTCVendor advisory
  41. 2026-09-27 19:06 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  42. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  43. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  44. 2026-09-25 04:59 UTCEG score recompute
  45. 2026-09-25 04:59 UTCVendor advisory
  46. 2026-09-25 04:59 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  47. 2026-09-24 10:06 UTCVendor advisory
  48. 2026-09-24 10:06 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  49. 2026-09-23 21:34 UTCEG score recompute
  50. 2026-09-23 21:34 UTCVendor advisory
  51. 2026-09-23 21:34 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  52. 2026-09-23 03:56 UTCVendor advisory
  53. 2026-09-23 03:56 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  54. 2026-09-22 15:24 UTCEG score recompute
  55. 2026-09-22 15:24 UTCVendor advisory
  56. 2026-09-22 15:24 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  57. 2026-09-20 21:25 UTCEG score recompute
  58. 2026-09-20 21:25 UTCVendor advisory
  59. 2026-09-20 21:25 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  60. 2026-09-19 23:50 UTCEG score recompute
  61. 2026-09-19 23:50 UTCVendor advisory
  62. 2026-09-19 23:50 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  63. 2026-09-19 04:22 UTCEG score recompute
  64. 2026-09-19 04:22 UTCVendor advisory
  65. 2026-09-19 04:22 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  66. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  67. 2026-09-18 14:55 UTCVendor advisory
  68. 2026-09-18 14:55 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  69. 2026-09-18 01:24 UTCEG score recompute
  70. 2026-09-18 01:24 UTCVendor advisory
  71. 2026-09-18 01:24 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  72. 2026-09-17 01:30 UTCEG score recompute
  73. 2026-09-17 01:30 UTCVendor advisory
  74. 2026-09-17 01:30 UTCGHSA enrichmentGHSA-cf63-g57m-mc5r · GitHub severity HIGH · GitHub CVSS 7.3
  75. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-16527?
CVE-2026-16527 is a high-severity vulnerability; its CVE record was published on July 30, 2026. An unauthenticated remote attacker can bypass access controls by sending crafted requests to the PCP pmproxy /store endpoint. This allows the attacker to overwrite any PMDA metric, leading to arbitrary code execution and system takeover.
When was CVE-2026-16527 made public?
CVE-2026-16527 was made public on July 30, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 30, 2026. EchelonGraph's copy of the record carries a last-modified date of October 2, 2026; the record at its source may have been updated since.
Is CVE-2026-16527 actively exploited?
CVE-2026-16527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16527?
CVE-2026-16527 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16527?
A fix for CVE-2026-16527 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-16527 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-16527

Explore →

Is Your Infrastructure Affected by CVE-2026-16527?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs