CVE-2026-16531

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2026-07-30. A secondary CVSS source baseline 5.3; sources differ by 0.0.

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

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

An unauthenticated remote attacker can exploit a path traversal vulnerability in the PCP pmproxy logger servlet using a crafted hostname. This allows arbitrary file and directory creation, potentially leading to a denial of service.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/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)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.4% × 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

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

August 21, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
No fix on record yet. Sources: redhat.
Red Hat

2506037 – (CVE-2026-16531) CVE-2026-16531 PCP: PCP: Arbitrary file creation via path traversal in pmproxy logger servlet

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

cve-details

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

Vendor Advisories for CVE-2026-16531(1)

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

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(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 57× 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 192 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 92 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.4% · 27th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 27th 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.4% · 27th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-06 23:55 UTCEG score recompute
  14. 2026-10-06 23:55 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-05 20:07 UTCEG score recompute
  17. 2026-10-05 20:06 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  18. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-04 06:44 UTCEG score recompute
  21. 2026-10-04 06:44 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  22. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-02 17:02 UTCEG score recompute
  24. 2026-10-02 17:02 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  25. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 75 more
  1. 2026-10-01 03:18 UTCEG score recompute
  2. 2026-10-01 03:18 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  3. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  5. 2026-09-29 06:57 UTCEG score recompute
  6. 2026-09-29 06:57 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  8. 2026-09-27 19:05 UTCEG score recompute
  9. 2026-09-27 19:05 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  10. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  11. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  12. 2026-09-25 04:59 UTCEG score recompute
  13. 2026-09-25 04:59 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  14. 2026-09-23 21:33 UTCEG score recompute
  15. 2026-09-23 21:33 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  16. 2026-09-22 15:24 UTCEG score recompute
  17. 2026-09-22 15:24 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  18. 2026-09-20 05:18 UTCEG score recompute
  19. 2026-09-20 05:18 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  20. 2026-09-19 05:19 UTCEG score recompute
  21. 2026-09-19 05:19 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-09-18 05:47 UTCEG score recompute
  24. 2026-09-18 05:47 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  25. 2026-09-17 06:15 UTCEG score recompute
  26. 2026-09-17 06:15 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  27. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-09-16 06:42 UTCEG score recompute
  29. 2026-09-16 06:42 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  30. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  31. 2026-09-15 07:09 UTCEG score recompute
  32. 2026-09-15 07:09 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  33. 2026-09-14 05:10 UTCEG score recompute
  34. 2026-09-14 05:10 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  35. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  36. 2026-09-13 05:38 UTCEG score recompute
  37. 2026-09-13 05:38 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  38. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-09-12 06:06 UTCEG score recompute
  40. 2026-09-12 06:06 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  41. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  42. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  43. 2026-09-11 06:32 UTCEG score recompute
  44. 2026-09-11 06:32 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  45. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  46. 2026-09-10 06:59 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  47. 2026-09-09 07:23 UTCEG score recompute
  48. 2026-09-09 07:23 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  49. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  50. 2026-09-07 20:10 UTCEG score recompute
  51. 2026-09-07 20:10 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  52. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  53. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  54. 2026-09-06 10:58 UTCEG score recompute
  55. 2026-09-06 10:58 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  56. 2026-09-05 11:26 UTCEG score recompute
  57. 2026-09-05 11:26 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  58. 2026-09-04 11:36 UTCEG score recompute
  59. 2026-09-04 11:36 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  60. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  61. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  62. 2026-09-01 23:12 UTCEG score recompute
  63. 2026-09-01 23:12 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  64. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  65. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  66. 2026-08-31 23:38 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  67. 2026-08-30 22:14 UTCEG score recompute
  68. 2026-08-30 22:14 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  69. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  70. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  71. 2026-08-29 22:42 UTCEG score recompute
  72. 2026-08-29 22:42 UTCGHSA enrichmentGHSA-2g52-w93h-w9v5 · GitHub CVSS 5.3
  73. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  74. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  75. 2026-08-27 10:49 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-16531?
CVE-2026-16531 is a medium-severity vulnerability; its CVE record was published on July 30, 2026. An unauthenticated remote attacker can exploit a path traversal vulnerability in the PCP pmproxy logger servlet using a crafted hostname. This allows arbitrary file and directory creation, potentially leading to a denial of service.
When was CVE-2026-16531 made public?
CVE-2026-16531 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 August 21, 2026; the record at its source may have been updated since.
Is CVE-2026-16531 actively exploited?
CVE-2026-16531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16531?
CVE-2026-16531 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16531?
No fix for CVE-2026-16531 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-16531 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-16531

Explore →

Is Your Infrastructure Affected by CVE-2026-16531?

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

Book a Demo →Browse All CVEs