EUVD-2026-70785

MOOS core-moos through 10.4.0 contains a remote process termination vulnerability in the SuicidalSleeper component that uses a hard-coded passphrase for multicast command authorization. Any multicast-reachable peer can enumerate MOOS processes and send termination commands to trigger process...

EUVD-2026-70789

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

EUVD-2026-70784

MOOS core-moos through 10.4.0 contains a denial of service vulnerability in the MOOSDB HTTP server that creates unbounded connections and threads without limits. Attackers can open many connections and send endless header data to exhaust server threads and memory, causing service unavailability...

EUVD-2026-70788

MOOS core-moos through 10.4.0 contains a buffer overflow vulnerability in CMOOSSerialPort::GetTelegram that writes a NUL terminator one byte past the serial telegram stack buffer. Attackers controlling the serial line can send a full-length telegram to trigger the off-by-one write, corrupting the...

EUVD-2026-70787

MOOS core-moos through 10.4.0 fails to escape database contents when rendering MOOSDB HTTP pages, allowing attackers to inject malicious scripts. Any MOOS publisher can set variable values containing script payloads that execute in the browser of operators viewing the web interface...

EUVD-2026-70775

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

EUVD-2026-70800

MOOS core-moos through 10.4.0 contains a pre-authentication heap overflow vulnerability in MOOSCommPkt packet handling that allows remote attackers to write arbitrary data by declaring a negative packet length. Attackers can exploit the signed integer check in InflateTo and negative size conversi...

EUVD-2026-70777

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

EUVD-2026-70776

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

EUVD-2026-70808

MOOS core-moos through 10.4.0 fails to validate client identity in MOOSDB message processing, allowing authenticated attackers to attribute writes to other clients by supplying arbitrary source identifiers in serialized messages. Attackers can forge message origins and cancel third-party...

EUVD-2026-70812

MOOS core-moos through 10.4.0 contains an authentication bypass vulnerability in the optional MOOSDB HTTP server that allows unauthenticated clients to write variables. Attackers can send HTTP requests with variable names and values to the MOOSDB HTTP server port to modify MOOS variables includin...

EUVD-2026-70816

MOOS core-moos through 10.4.0 lacks authentication in the wire protocol, allowing unauthenticated clients to connect with full publish, subscribe, and database clear privileges. Attackers can bypass the compile-time protocol string check and connect with arbitrary client names to execute privileg...

CVE-2026-85454

MOOS core-moos through 10.4.0 contains an off-by-one buffer overflow in CMOOSSerialPort::GetTelegram(), where a NUL terminator is written one byte past the serial telegram stack buffer. An attacker with physical access to the serial line can send a full-length telegram to trigger the write, corru...

CVE-2026-85455

MOOS core-moos through 10.4.0 contains a buffer over-read in the CMOOSCommPkt component. A crafted four-byte packet sent over a TCP connection to the MOOSDB port triggers an out-of-bounds memory access during deserialization, allowing an unauthenticated attacker to read process memory. The vulner...

CVE-2026-85451

MOOS core-moos through 10.4.0 is affected by a remote process termination vulnerability in the SuicidalSleeper component. The root cause is a hard-coded passphrase used for multicast command authorization, allowing any multicast-reachable peer to enumerate MOOS processes and send termination comm...

CVE-2026-85450

MOOS core-moos through version 10.4.0 contains a denial of service vulnerability in its MOOSDB HTTP server component. The root cause is the creation of unbounded connections and threads without limits , allowing an attacker over the network (no authentication required) to open many connections an...

CVE-2026-85443

MOOS core-moos through 10.4.0 has a denial of service vulnerability in MOOSCommServer::ListenLoop(). The accept thread performs a blocking receive without timeout during the wire-protocol handshake. An unauthenticated network attacker can open a TCP connection to the MOOSDB port and send no data,...

CVE-2026-85442

MOOS core-moos versions through 10.4.0 fail to validate packet length declarations in CMOOSCommPkt::OnBytesWritten() (source file: Core/libMOOS/Comms/MOOSCommPkt.cpp, line 99). An unauthenticated attacker on the network can send crafted wire packets with large declared lengths, triggering unbound...

CVE-2026-85441

MOOS core-moos through 10.4.0 contains a denial-of-service vulnerability in CMOOSMsg::operator>> , which fails to validate that serialized string lengths are non-negative. An unauthenticated attacker can send a crafted message with a negative length value to the MOOSDB port , triggering an ...

CVE-2026-85432

MOOS core-moos through 10.4.0, an underwater robotics middleware, contains a message source spoofing flaw in its MOOSDB message processing layer. The root cause is a failure to validate client identity: the system trusts wire-supplied source identifiers in serialized messages rather than the auth...