MOOS core-moos through 10.4.0 contains a denial of service vulnerability in MOOSCommServer::ListenLoop() where the accept thread performs a blocking receive without timeout during the wire-protocol handshake. An attacker can open a TCP connection to the MOOSDB port and send no data, causing the accept thread to block indefinitely while holding the socket-list lock, preventing all subsequent client connections.
CVE-2026-85443
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.
- High severity, but no confirmed exploitation yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/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)Severity75% × 45%The EG Score, 7.5 of 10.Exploitation0.6% × 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 partial (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.6%
- EPSS %ILE
- 48th
- 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 partial (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; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 14, 2026
Advisory Details (5)
Auto-updated Sep 3, 2026MOOS core-moos through 10.4.0 MOOSDB Accept Loop Denial of Service | Advisories | VulnCheck
https://www.vulncheck.com/advisories/moos-core-moos-through-10.4.0-moosdb-accept-loop-denial-of-servicecore-moos/Core/libMOOS/Comms/MOOSCommServer.cpp at ec9c77c68fcbdef8f5e4c60fe243acd223433f0c · themoos/core-moos · GitHub
https://github.com/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243acd223433f0c/Core/libMOOS/Comms/MOOSCommServer.cpp#L922GitHub - 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-mooscommit 8d940303949a (themoos/core-moos)
Fix landed in themoos/core-moos commit 8d940303949a — awaiting tagged release
https://github.com/themoos/core-moos/commit/8d940303949a850d4625eca2a60f27adee9c3ec4Give the wire protocol read on the accept thread a timeout
Upstream fix in progress (PR #83 · themoos/core-moos, state=open)
https://github.com/themoos/core-moos/pull/83Vendor Advisories for CVE-2026-85443(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 / 118× 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 149 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 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-11 19:17 UTCEG score recompute
- 2026-10-11 16:34 UTCEG score recompute
- 2026-10-11 13:51 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-10 11:12 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-09 23:24 UTCEG score recompute
- 2026-10-09 23:24 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-09 01:23 UTCEG score recompute
- 2026-10-09 01:22 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-07 23:23 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-07 07:02 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-06 19:09 UTCEG score recompute
- 2026-10-06 19:09 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-06 07:15 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-05 19:08 UTCEG score recompute
- 2026-10-05 19:08 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-05 07:20 UTCEG score recompute
- 2026-10-05 07:20 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
Show 75 moreShow fewer
- 2026-10-04 19:31 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-04 07:03 UTCEG score recompute
- 2026-10-04 07:03 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-03 19:14 UTCEG score recompute
- 2026-10-03 19:14 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-03 07:05 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-02 19:16 UTCEG score recompute
- 2026-10-02 19:16 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-02 07:25 UTCEG score recompute
- 2026-10-02 07:25 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-10-01 19:37 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-01 06:53 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-30 19:04 UTCEG score recompute
- 2026-09-30 19:04 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-09-30 02:50 UTCEG score recompute
- 2026-09-30 02:50 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-29 14:56 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-29 02:58 UTCEG score recompute
- 2026-09-29 02:58 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-28 15:09 UTCEG score recompute
- 2026-09-28 15:08 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-09-28 03:10 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-27 15:22 UTCEG score recompute
- 2026-09-27 15:22 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-09-27 03:18 UTCEG score recompute
- 2026-09-27 03:18 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
- 2026-09-26 15:28 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-26 03:39 UTCEG score recompute
- 2026-09-26 03:39 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-25 11:14 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-24 23:17 UTCEG score recompute
- 2026-09-24 23:17 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
- 2026-09-24 11:13 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-23 23:25 UTCEG score recompute
- 2026-09-23 23:25 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-23 11:29 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-22 23:40 UTCEG score recompute
- 2026-09-22 23:40 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-22 11:51 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-22 00:02 UTCEG score recompute
- 2026-09-22 00:02 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-21 12:13 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-21 00:25 UTCEG score recompute
- 2026-09-21 00:24 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-20 12:31 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-20 00:39 UTCEG score recompute
- 2026-09-20 00:39 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-19 12:50 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-19 01:02 UTCEG score recompute
- 2026-09-19 01:02 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-18 13:13 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-18 01:24 UTCEG score recompute
- 2026-09-18 01:24 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-17 13:36 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-17 01:47 UTCEG score recompute
- 2026-09-17 01:47 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-16 13:58 UTCEG score recompute
- 2026-09-16 13:58 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-16 01:59 UTCGHSA enrichmentGHSA-qqc5-c4q6-4q3x · GitHub severity HIGH · GitHub CVSS 7.5
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-85443?
When was CVE-2026-85443 made public?
Is CVE-2026-85443 actively exploited?
What is the CVSS score of CVE-2026-85443?
How do I remediate CVE-2026-85443?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-85443
Is Your Infrastructure Affected by CVE-2026-85443?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.