CyberSecBulletin

Themoos vulnerabilities

We track 16 vulnerabilities in Themoos products across 3 products. 16 are rated high or critical, and none are known to be exploited. The most recent was published on September 3, 2026.

16vulnerabilities
6critical
10high
0exploited
8.5average CVSS score

Latest Themoos vulnerabilities

  • 8.2 High severity

    core-moos: Out-of-bounds Read

    CVE-2026-85455Themoos

    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

  • 8.8 High severity

    ui-moos: Out-of-bounds Write

    CVE-2026-85452Themoos

    MOOS ui-moos through 50b9c6c contains a buffer overflow vulnerability in ScopeTabPane.cpp and ScopeGrid.cpp where client and variable names are formatted into fixed 1024-byte buffers using sprintf without length validation. Attackers can supply arbitrarily lon

  • 7.1 High severity

    core-moos: Use of Hard-coded Credentials

    CVE-2026-85451Themoos

    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 termina

  • 7.5 High severity

    core-moos: Allocation of Resources Without Limits or Throttling

    CVE-2026-85450Themoos

    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 mem

  • 7.5 High severity

    core-moos: Uncontrolled Resource Consumption

    CVE-2026-85443Themoos

    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

  • 7.5 High severity

    core-moos: Memory Allocation with Excessive Size Value

    CVE-2026-85442Themoos

    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 decla

  • 7.5 High severity

    core-moos: Signed to Unsigned Conversion Error

    CVE-2026-85441Themoos

    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 t

  • 9.8 Critical severity

    core-moos: Out-of-bounds Write

    CVE-2026-85440ThemoosEPSS 1.03%

    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

  • 7.5 High severity

    essential-moos: Integer Underflow (Wrap or Wraparound)

    CVE-2026-85436ThemoosEPSS 2.08%

    MOOS essential-moos through 10.0.1 contains a buffer overflow vulnerability in CMOOSUDPLink::ReadPktFromArray() that allows remote attackers to corrupt heap memory by sending UDP datagrams with negative declared lengths. Attackers can send crafted UDP packets

  • 9.8 Critical severity

    essential-moos: Missing Authorization

    CVE-2026-85433Themoos

    MOOS essential-moos pShare through 10.0.1 fails to properly authorize PSHARE_CMD messages, allowing any publisher to reconfigure network routes and listeners at runtime. Attackers can send crafted PSHARE_CMD messages with cmd=output or cmd=input parameters to

  • 8.2 High severity

    core-moos: Authentication Bypass by Spoofing

    CVE-2026-85432Themoos

    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 or

  • 7.5 High severity

    essential-moos: Insufficient Verification of Data Authenticity

    CVE-2026-85431ThemoosEPSS 3.37%

    MOOS essential-moos through version 10.0.1 contains an unauthenticated UDP packet injection vulnerability in pMOOSBridge when configured with UDPListen. Attackers can send crafted UDP packets to the configured port to inject arbitrary variables into the local

  • 9.1 Critical severity

    essential-moos: Insufficient Verification of Data Authenticity

    CVE-2026-85430ThemoosEPSS 1.66%

    MOOS essential-moos through 10.0.1 contains an authentication bypass vulnerability in pShare that accepts UDP datagrams from any source and republishes them with the attacker-claimed identity intact. Attackers can send crafted UDP datagrams to pShare input rou

  • 9.8 Critical severity

    core-moos: Missing Authentication for Critical Functionality

    CVE-2026-85428Themoos

    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 p

  • 9.8 Critical severity

    essential-moos: Download of Code Without Integrity Check

    CVE-2026-85427Themoos

    MOOS essential-moos pAntler through 10.0.1 contains a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary programs by publishing a crafted MISSION_FILE message to the MOOSDB. Attackers can publish a mission file conta

  • 9.8 Critical severity

    core-moos: Missing Authentication for Critical Functionality

    CVE-2026-85424Themoos

    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 arbit