CVE-2026-85441

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
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.5Exploit: None knownExposed: 0

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

MOOS core-moos through 10.4.0 fails to validate that serialized string lengths are non-negative in CMOOSMsg::operator>>. Unauthenticated attackers can send a crafted message with a negative length value to the MOOSDB port, causing an unhandled exception that terminates the database process.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

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.
generic

MOOS core-moos through 10.4.0 MOOSDB Denial of Service via Negative Serialized String Length | Advisories | VulnCheck

https://www.vulncheck.com/advisories/moos-core-moos-through-10.4.0-moosdb-denial-of-service-via-negative-serialized-string-length
generic

core-moos/Core/libMOOS/Comms/MOOSMsg.cpp at ec9c77c68fcbdef8f5e4c60fe243acd223433f0c · themoos/core-moos · GitHub

https://github.com/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243acd223433f0c/Core/libMOOS/Comms/MOOSMsg.cpp#L453
generic

GitHub - themoos/core-moos: A very light weight, easy to use middleware. You will need core-moos above all other components · GitHub

https://github.com/themoos/core-moos
github_commit

commit 04c92981091f (themoos/core-moos)

Fix landed in themoos/core-moos commit 04c92981091f — awaiting tagged release

https://github.com/themoos/core-moos/commit/04c92981091fdaa2ff85e2ba7eff94f6288bdbaf
github_pr

Refuse negative lengths when deserialising a CMOOSMsg

Upstream fix in progress (PR #74 · themoos/core-moos, state=open)

https://github.com/themoos/core-moos/pull/74

Vendor Advisories for CVE-2026-85441(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 27× in last 7d / 63× 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.

  1. 2026-09-19 12:13 UTCGHSA enrichment
  2. 2026-09-19 00:35 UTCEG score recompute
  3. 2026-09-19 00:35 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 12:58 UTCGHSA enrichment
  6. 2026-09-18 01:20 UTCEG score recompute
  7. 2026-09-18 01:20 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 13:42 UTCGHSA enrichment
  10. 2026-09-17 02:05 UTCGHSA enrichment
  11. 2026-09-16 14:27 UTCEG score recompute
  12. 2026-09-16 14:27 UTCGHSA enrichment
  13. 2026-09-16 14:09 UTCEPSS rescore
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-16 02:48 UTCGHSA enrichment
  16. 2026-09-15 15:10 UTCGHSA enrichment
  17. 2026-09-15 03:32 UTCEG score recompute
  18. 2026-09-15 03:32 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 15:54 UTCGHSA enrichment
  22. 2026-09-14 04:17 UTCEG score recompute
  23. 2026-09-14 04:17 UTCGHSA enrichment
  24. 2026-09-13 16:39 UTCGHSA enrichment
  25. 2026-09-13 05:02 UTCGHSA enrichment
Show 38 more
  1. 2026-09-12 17:24 UTCEG score recompute
  2. 2026-09-12 17:24 UTCGHSA enrichment
  3. 2026-09-12 05:46 UTCGHSA enrichment
  4. 2026-09-11 18:09 UTCEG score recompute
  5. 2026-09-11 18:09 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 06:31 UTCGHSA enrichment
  9. 2026-09-10 18:53 UTCEG score recompute
  10. 2026-09-10 18:53 UTCGHSA enrichment
  11. 2026-09-10 07:13 UTCGHSA enrichment
  12. 2026-09-09 19:35 UTCGHSA enrichment
  13. 2026-09-09 07:57 UTCEG score recompute
  14. 2026-09-09 07:57 UTCGHSA enrichment
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-08 20:19 UTCGHSA enrichment
  17. 2026-09-08 11:43 UTCGHSA enrichment
  18. 2026-09-07 23:54 UTCEG score recompute
  19. 2026-09-07 23:53 UTCGHSA enrichment
  20. 2026-09-07 12:15 UTCGHSA enrichment
  21. 2026-09-07 00:34 UTCEG score recompute
  22. 2026-09-07 00:34 UTCGHSA enrichment
  23. 2026-09-06 13:48 UTCEPSS rescore
  24. 2026-09-06 12:56 UTCGHSA enrichment
  25. 2026-09-06 01:18 UTCEG score recompute
  26. 2026-09-06 01:18 UTCGHSA enrichment
  27. 2026-09-05 15:31 UTCEPSS rescore
  28. 2026-09-05 13:38 UTCGHSA enrichment
  29. 2026-09-05 01:57 UTCGHSA enrichment
  30. 2026-09-04 14:19 UTCEG score recompute
  31. 2026-09-04 14:19 UTCGHSA enrichment
  32. 2026-09-04 13:45 UTCEG score recompute
  33. 2026-09-04 13:45 UTCGHSA enrichment
  34. 2026-09-04 11:07 UTCEG score recompute
  35. 2026-09-04 11:07 UTCGHSA enrichment
  36. 2026-09-03 23:29 UTCEG score recompute
  37. 2026-09-03 22:44 UTCEG score recompute
  38. 2026-09-03 22:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85441?
CVE-2026-85441 is a high vulnerability published on September 3, 2026. MOOS core-moos through 10.4.0 fails to validate that serialized string lengths are non-negative in CMOOSMsg::operator>>. Unauthenticated attackers can send a crafted message with a negative length value to the MOOSDB port, causing an unhandled exception that terminates the database process.
When was CVE-2026-85441 disclosed?
CVE-2026-85441 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85441 actively exploited?
CVE-2026-85441 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 69.6% of all scored CVEs.
What is the CVSS score of CVE-2026-85441?
CVE-2026-85441 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-85441?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85441, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85441?

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

Start Free Scan →Browse All CVEs