# CVE-2026-85455: MOOS core-moos buffer over-read in CMOOSCommPkt deserialization

Source: https://junglewise.ai/threats/cve-2026-85455-moos-core-moos-buffer-over-read-in-cmooscommpkt-deserialization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-03. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-85455 · Severity: high · CVSS 8.2 · Published 2026-09-03

MOOS is a lightweight middleware messaging system used in robotics and autonomous systems. A buffer over-read vulnerability in the packet deserialization layer allows unauthenticated remote attackers to read sensitive memory by sending a malformed packet to the MOOSDB server port, potentially exposing credentials, encryption keys, or other sensitive data.

Technologies: [MOOS Core-Moos](https://junglewise.ai/threats/technologies/core-moos). Vendors: [MOOS](https://junglewise.ai/threats/vendors/moos).

## Quick answers

**Is CVE-2026-85455 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-85455 being exploited in the wild.

**How severe is CVE-2026-85455?** High severity, with a CVSS score of 8.2, published 3 September 2026.

**Which products and versions are affected?** MOOS Core-Moos through 10.4.0.

**Is there a fix for CVE-2026-85455?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-85455 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-85455?** Check whether you run MOOS Core-Moos at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a buffer over-read in CMOOSCommPkt's deserialization logic that occurs when processing an abnormally short (four-byte) packet. The vulnerable component fails to validate packet length before attempting to read structured data from the buffer, resulting in out-of-bounds memory access. Attack vector is network-based via a direct TCP connection to the MOOSDB port; no authentication is required prior to exploitation. An attacker can read arbitrary memory contents from the affected process, disclosing sensitive information such as configuration data, credentials, or cryptographic material. Versions through 10.4.0 are affected.

## Affected products

- MOOS core-moos through 10.4.0

## Timeline

- 2026-09-03: disclosed

## References

- [https://github.com/themoos/core-moos](https://github.com/themoos/core-moos)
- [https://github.com/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243acd223433f0c/Core/libMOOS/Comms/MOOSCommPkt.cpp](https://github.com/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243acd223433f0c/Core/libMOOS/Comms/MOOSCommPkt.cpp)

## Related threats

- [MOOS core-moos buffer overflow in CMOOSSerialPort](https://junglewise.ai/threats/cve-2026-85454-moos-core-moos-buffer-overflow-in-cmoosserialport)
- [MOOS core-moos DOM-based XSS in HTTP MOOSDB interface](https://junglewise.ai/threats/cve-2026-85453-moos-core-moos-dom-based-xss-in-http-moosdb-interface)
- [MOOS core-moos remote process termination via hardcoded multicast passphrase](https://junglewise.ai/threats/cve-2026-85451-moos-core-moos-remote-process-termination-via-hardcoded-multicast)
- [MOOS core-moos denial of service in MOOSDB HTTP server](https://junglewise.ai/threats/cve-2026-85450-moos-core-moos-denial-of-service-in-moosdb-http-server)
- [MOOS core-moos denial of service in MOOSCommServer](https://junglewise.ai/threats/cve-2026-85443-moos-core-moos-denial-of-service-in-mooscommserver)