CVE-2026-85455 json
MOOS core-moos through 10.4.0 MOOSDB Out-of-Bounds Read via Short Packet
published 2026-09-03 2 mo ago modified 2026-10-14 25 d ago also EUVD-2026-70789
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
MOOS core-moos through 10.4.0 contains a buffer over-read vulnerability in CMOOSCommPkt where a four-byte packet triggers out-of-bounds memory access during deserialization. Attackers can open a TCP connection to the MOOSDB port and send a crafted short packet to read memory before authentication.
Patch / fix
- themoos core-moos 10.4.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.8 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H |
| CNA | 4.0 | 8.8 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- themoos core-moos
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/themoos/core-moos/pull/75
issue-tracking, patch
-
github.com
/themoos/core-moos/commit/d30c14585753f9ae39749d9628ed15c8383f0568
patch, issue-tracking
-
github.com
/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243acd223433f0c/Core/libMOOS/Comms/MOOSCommPkt.cpp#L228
technical-description, issue-tracking, patch
-
github.com
/themoos/core-moos
product
-
vulncheck.com
/advisories/moos-core-moos-through-10.4.0-moosdb-out-of-bounds-read-via-short-packet
third-party-advisory
Sources
- CVE List CVE-2026-85455
- NVD CVE-2026-85455
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.