CVE-2026-16527

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

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, ghsa, secondary
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

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.3(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

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
Severity73% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 21, 2026

Advisory Details (2)

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

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
redhat Patch Available

cve-details

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

Vendor Advisories for CVE-2026-16527(1)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpcp-0:7.0.3-5.el10_22026-08-17redhat
redhatpcp-0:5.3.7-22.el8_10.52026-08-17redhat
redhatpcp-0:6.3.7-8.el9_8.42026-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 rangeFixed inDependents
pcp5.2.6-1 ... 7.2.0-1 (44 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pcp6.0.3-1.1 ... 7.2.0-1 (30 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pcp6.3.8-1 ... 7.2.0-1 (14 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pcp6.3.8-1 ... 7.2.0-1 (14 versions)——

Weakness Classification(2)

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

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 146× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 154 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-16527?
CVE-2026-16527 is a high vulnerability 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 disclosed?
CVE-2026-16527 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16527 actively exploited?
CVE-2026-16527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.5% of all scored CVEs.
What is the CVSS score of CVE-2026-16527?
CVE-2026-16527 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-16527?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16527, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs