CVE-2026-85426

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-04. A secondary CVSS source baseline 9.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
9.8EG
EchelonGraph verdictPlan mitigationRemediate 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.9%CVSS: 9.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

MOOS-IvP uMemWatch through 24.8.1 constructs shell commands from attacker-chosen MOOS client names without sanitization. Attackers can inject shell metacharacters into client names to execute arbitrary commands as the uMemWatch process user through unquoted redirection targets in system calls.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.9% × 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 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: An upstream fix is merged but not yet in a tagged release. 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 until it ships, then apply the release.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

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

An upstream fix is merged but not yet in a tagged release. 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 until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 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 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

September 3, 2026

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Oct 7, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
Web page

MOOS-IvP through 24.8.1 uMemWatch Command Injection via MOOS Client Names | Advisories | VulnCheck

https://www.vulncheck.com/advisories/moos-ivp-through-24.8.1-umemwatch-command-injection-via-moos-client-names
GitHub pull request

uMemWatch: measure memory without a shell

Upstream fix in progress (PR #121 · moos-ivp/moos-ivp, state=closed)

https://github.com/moos-ivp/moos-ivp/pull/121
GitHub commit

commit 0b2bd991b0ca (moos-ivp/moos-ivp)

Fix landed in moos-ivp/moos-ivp commit 0b2bd991b0ca — awaiting tagged release

https://github.com/moos-ivp/moos-ivp/commit/0b2bd991b0ca7139b1edcf271473d33e7eccfc20
Web page

moos-ivp/ivp/src/uMemWatch/MemWatch.cpp at 1de9ae146cd63c209e8c3fd81611a4ed2472971b · moos-ivp/moos-ivp · GitHub

https://github.com/moos-ivp/moos-ivp/blob/1de9ae146cd63c209e8c3fd81611a4ed2472971b/ivp/src/uMemWatch/MemWatch.cpp#L182
Web page

GitHub - moos-ivp/moos-ivp: MOOS-IvP is a set of modules for providing autonomy on robotic platforms, in particular autonomous marine vehicles. · GitHub

https://github.com/moos-ivp/moos-ivp

Vendor Advisories for CVE-2026-85426(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 43× in last 7d / 216× 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 282 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 182 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85426?
CVE-2026-85426 is a critical-severity vulnerability; its CVE record was published on September 3, 2026. MOOS-IvP uMemWatch through 24.8.1 constructs shell commands from attacker-chosen MOOS client names without sanitization. Attackers can inject shell metacharacters into client names to execute arbitrary commands as the uMemWatch process user through unquoted redirection targets in system calls.
When was CVE-2026-85426 made public?
CVE-2026-85426 was made public on September 2, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 3, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-85426 actively exploited?
CVE-2026-85426 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85426?
CVE-2026-85426 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85426?
An upstream fix for CVE-2026-85426 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-85426 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85426?

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

Book a Demo →Browse All CVEs