CVE-2026-72573

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.6%CVSS: 8.8Exploit: 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 OS command injection vulnerability in 4xmen/pm2panel (all versions) allows an authenticated remote attacker to execute arbitrary system commands on the host. The pm2panel.js handler at line 188 passes the unsanitized req.query.id parameter directly to exec('pm2 restart ' + id) without input validation or shell escaping, enabling command chaining via semicolons or other shell metacharacters.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation1.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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, and watch the vendor's advisory for the fix.
EPSS PROB
1.6%
EPSS %ILE
74th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

August 10, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Aug 10, 2026
No fix on record yet.
Web page

GitHub - 4xmen/pm2panel: pm2 web control panel to manager process with web ui · GitHub

https://github.com/4xmen/pm2panel

Vendor Advisories for CVE-2026-72573(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 78× 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 202 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 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72573?
CVE-2026-72573 is a high-severity vulnerability; its CVE record was published on August 10, 2026. An OS command injection vulnerability in 4xmen/pm2panel (all versions) allows an authenticated remote attacker to execute arbitrary system commands on the host. The pm2panel.js handler at line 188 passes the unsanitized req.query.id parameter directly to exec('pm2 restart ' + id) without input…
When was CVE-2026-72573 made public?
CVE-2026-72573 was made public on August 10, 2026: that is the date its CVE record's CNA, Turan Security, gives for when the vulnerability was made public. The CVE record itself was published on August 10, 2026. EchelonGraph's copy of the record carries a last-modified date of September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-72573 actively exploited?
CVE-2026-72573 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72573?
CVE-2026-72573 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72573?
No fix for CVE-2026-72573 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-72573 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72573

Explore →

Is Your Infrastructure Affected by CVE-2026-72573?

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

Book a Demo →Browse All CVEs