CVE-2026-85439

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. A secondary CVSS source baseline 7.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
7.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: 0.4%CVSS: 7.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 through 24.8.1 contains a remote code execution vulnerability in alogsplit's SplitHandler::handlePreCheckSplitDir() function that fails to sanitize shell metacharacters in log file pathnames. Attackers can embed shell syntax in log file names or the --dir parameter to execute arbitrary commands with the privileges of the operator running alogsplit.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.4% × 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: 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 until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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 until it ships, then apply the release.

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

September 3, 2026

Last Modified

September 8, 2026

Advisory Details (5)

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

MOOS-IvP through 24.8.1 alogsplit Command Injection via Input Pathname | Advisories | VulnCheck

https://www.vulncheck.com/advisories/moos-ivp-through-24.8.1-alogsplit-command-injection-via-input-pathname
Web page

moos-ivp/ivp/src/lib_logutils/SplitHandler.cpp at 1de9ae146cd63c209e8c3fd81611a4ed2472971b · moos-ivp/moos-ivp · GitHub

https://github.com/moos-ivp/moos-ivp/blob/1de9ae146cd63c209e8c3fd81611a4ed2472971b/ivp/src/lib_logutils/SplitHandler.cpp#L608
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
GitHub commit

commit f684d77d9d6e (moos-ivp/moos-ivp)

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

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

alogsplit: create the split directory without a shell

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

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

Vendor Advisories for CVE-2026-85439(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 25× in last 7d / 108× 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 99 of 142 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 43 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.4% · 30th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-10 12:19 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-09 23:25 UTCEG score recompute
  8. 2026-10-09 23:24 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-09 01:23 UTCEG score recompute
  11. 2026-10-09 01:23 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-07 23:23 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-07 08:11 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-06 19:16 UTCEG score recompute
  17. 2026-10-06 19:16 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-10-06 06:22 UTCEG score recompute
  20. 2026-10-06 06:22 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-10-05 16:40 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-05 03:34 UTCEG score recompute
  24. 2026-10-05 03:34 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 74 more
  1. 2026-10-04 14:39 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-04 01:44 UTCEG score recompute
  3. 2026-10-04 01:44 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-03 12:42 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-02 22:52 UTCEG score recompute
  7. 2026-10-02 22:52 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-02 09:51 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-01 20:57 UTCEG score recompute
  11. 2026-10-01 20:57 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-01 08:01 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-09-30 19:05 UTCEG score recompute
  15. 2026-09-30 19:05 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-09-30 02:50 UTCEG score recompute
  18. 2026-09-30 02:50 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-09-29 09:55 UTCEG score recompute
  20. 2026-09-29 09:55 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-09-28 21:01 UTCEG score recompute
  22. 2026-09-28 21:01 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-09-28 08:05 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-09-27 19:11 UTCEG score recompute
  26. 2026-09-27 19:11 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  27. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-09-27 06:16 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-09-26 17:20 UTCEG score recompute
  30. 2026-09-26 17:20 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  32. 2026-09-26 04:15 UTCEG score recompute
  33. 2026-09-26 04:15 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  34. 2026-09-25 15:10 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-09-25 01:57 UTCEG score recompute
  36. 2026-09-25 01:57 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  37. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  38. 2026-09-24 13:02 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  39. 2026-09-24 00:06 UTCEG score recompute
  40. 2026-09-24 00:06 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  42. 2026-09-23 11:12 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  43. 2026-09-22 22:17 UTCEG score recompute
  44. 2026-09-22 22:17 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  45. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  46. 2026-09-22 09:22 UTCEG score recompute
  47. 2026-09-22 09:22 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  49. 2026-09-21 20:27 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-09-21 07:29 UTCEG score recompute
  51. 2026-09-21 07:29 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  53. 2026-09-20 18:06 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-09-20 05:01 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-09-19 16:07 UTCEG score recompute
  56. 2026-09-19 16:07 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-09-19 03:11 UTCEG score recompute
  58. 2026-09-19 03:11 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  60. 2026-09-18 14:17 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  61. 2026-09-18 01:10 UTCEG score recompute
  62. 2026-09-18 01:10 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  64. 2026-09-17 12:15 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-16 23:20 UTCEG score recompute
  66. 2026-09-16 23:20 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  68. 2026-09-16 10:25 UTCEG score recompute
  69. 2026-09-16 10:25 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  71. 2026-09-15 21:30 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-09-15 08:35 UTCEG score recompute
  73. 2026-09-15 08:35 UTCGHSA enrichmentGHSA-fm2r-qmc4-5wf2 · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 16th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85439?
CVE-2026-85439 is a high-severity vulnerability; its CVE record was published on September 3, 2026. MOOS-IvP through 24.8.1 contains a remote code execution vulnerability in alogsplit's SplitHandler::handlePreCheckSplitDir() function that fails to sanitize shell metacharacters in log file pathnames. Attackers can embed shell syntax in log file names or the --dir parameter to execute arbitrary…
When was CVE-2026-85439 made public?
CVE-2026-85439 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-85439 actively exploited?
CVE-2026-85439 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85439?
CVE-2026-85439 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85439?
An upstream fix for CVE-2026-85439 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-85439 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85439?

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

Book a Demo →Browse All CVEs