CVE-2026-85442

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 packet length declarations in CMOOSCommPkt::OnBytesWritten(), allowing unauthenticated attackers to trigger unbounded buffer allocation by sending crafted wire packets. Attackers can send packets with large declared lengths to exhaust server memory and cause denial of service before client authentication completes.

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
35%
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 Unbounded Packet Allocation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/moos-core-moos-through-10.4.0-moosdb-denial-of-service-via-unbounded-packet-allocation
generic

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

https://github.com/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243acd223433f0c/Core/libMOOS/Comms/MOOSCommPkt.cpp#L99
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 e7ea624a7b78 (themoos/core-moos)

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

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

Bound the declared packet length and contain allocation failure

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

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

Vendor Advisories for CVE-2026-85442(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 09:06 UTCGHSA enrichment
  2. 2026-09-18 21:23 UTCEG score recompute
  3. 2026-09-18 21:23 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 08:30 UTCGHSA enrichment
  6. 2026-09-17 20:47 UTCEG score recompute
  7. 2026-09-17 20:47 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 09:04 UTCGHSA enrichment
  10. 2026-09-16 21:20 UTCEG score recompute
  11. 2026-09-16 21:20 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 09:02 UTCEG score recompute
  14. 2026-09-16 09:02 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 21:10 UTCGHSA enrichment
  17. 2026-09-15 09:27 UTCEG score recompute
  18. 2026-09-15 09:27 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 21:44 UTCGHSA enrichment
  22. 2026-09-14 10:00 UTCGHSA enrichment
  23. 2026-09-13 22:17 UTCEG score recompute
  24. 2026-09-13 22:17 UTCGHSA enrichment
  25. 2026-09-13 10:34 UTCGHSA enrichment
Show 38 more
  1. 2026-09-12 22:49 UTCEG score recompute
  2. 2026-09-12 22:49 UTCGHSA enrichment
  3. 2026-09-12 11:06 UTCGHSA enrichment
  4. 2026-09-11 23:15 UTCEG score recompute
  5. 2026-09-11 23:15 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 10:51 UTCEG score recompute
  9. 2026-09-11 10:51 UTCGHSA enrichment
  10. 2026-09-10 23:08 UTCGHSA enrichment
  11. 2026-09-10 11:25 UTCEG score recompute
  12. 2026-09-10 11:25 UTCGHSA enrichment
  13. 2026-09-09 23:26 UTCGHSA enrichment
  14. 2026-09-09 08:02 UTCEG score recompute
  15. 2026-09-09 08:02 UTCGHSA enrichment
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-08 20:19 UTCGHSA enrichment
  18. 2026-09-08 05:27 UTCGHSA enrichment
  19. 2026-09-07 17:41 UTCEG score recompute
  20. 2026-09-07 17:41 UTCGHSA enrichment
  21. 2026-09-07 05:57 UTCGHSA enrichment
  22. 2026-09-06 18:15 UTCEG score recompute
  23. 2026-09-06 18:15 UTCGHSA enrichment
  24. 2026-09-06 13:48 UTCEPSS rescore
  25. 2026-09-06 06:31 UTCGHSA enrichment
  26. 2026-09-05 18:47 UTCEG score recompute
  27. 2026-09-05 18:47 UTCGHSA enrichment
  28. 2026-09-05 15:31 UTCEPSS rescore
  29. 2026-09-05 07:04 UTCGHSA enrichment
  30. 2026-09-04 19:21 UTCEG score recompute
  31. 2026-09-04 19:20 UTCGHSA enrichment
  32. 2026-09-04 18:49 UTCEG score recompute
  33. 2026-09-04 18:49 UTCGHSA enrichment
  34. 2026-09-04 11:13 UTCEG score recompute
  35. 2026-09-04 11:13 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-85442?
CVE-2026-85442 is a high vulnerability published on September 3, 2026. MOOS core-moos through 10.4.0 fails to validate packet length declarations in CMOOSCommPkt::OnBytesWritten(), allowing unauthenticated attackers to trigger unbounded buffer allocation by sending crafted wire packets. Attackers can send packets with large declared lengths to exhaust server memory…
When was CVE-2026-85442 disclosed?
CVE-2026-85442 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-85442 actively exploited?
CVE-2026-85442 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 64.8% of all scored CVEs.
What is the CVSS score of CVE-2026-85442?
CVE-2026-85442 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-85442?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85442, 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-85442

Explore →

Is Your Infrastructure Affected by CVE-2026-85442?

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