MOOSDB HTTP Server Authentication Bypass

Technical Analysis

CVE-2026-85428 (CVSS 9.8) stems from missing authentication checks in the MOOSDB HTTP server, a component commonly enabled for remote monitoring and telemetry in unmanned surface vehicles (USVs), autonomous underwater vehicles (AUVs), and robotics research platforms built on the MOOS-IvP middleware. Attackers can send crafted HTTP requests directly to the MOOSDB HTTP listener port to write variable name/value pairs, effectively injecting arbitrary actuator commands, overriding safety interlocks, or spoofing navigation and mission-state data without any credentials. Exploitation requires only network reachability to the exposed HTTP port, making internet-facing or poorly segmented deployments trivially exploitable for full behavioral control of the affected autonomous platform. This is a classic autonomy/robotics middleware flaw rather than a traditional IT vulnerability, but where MOOS-IvP nodes are integrated into AI-driven autonomous agent stacks (e.g., perception-to-actuation pipelines feeding decisions from ML models into MOOSDB variables), an attacker could silently override agent-issued commands or inject false sensor/state values, corrupting the agent's world model and downstream decision-making without detection.

Affected Systems

MOOS core-moos through version 10.4.0 with the optional MOOSDB HTTP server module enabled; deployments on unmanned surface vehicles (USVs), autonomous underwater vehicles (AUVs), robotics research platforms, and any system integrating MOOS-IvP middleware with network-exposed HTTP telemetry/control ports.

Indicators of Compromise

• Unusual/unauthorized HTTP requests to MOOSDB HTTP server ports (default commonly 9000-9010 range, deployment-dependent)
• HTTP requests containing variable name/value pairs targeting actuator or override-named MOOS variables
• Unexpected MOOS variable writes originating from unrecognized source IPs
• Anomalous actuator commands or navigation overrides not correlated with legitimate mission control traffic

Remediation Steps

1. 1

   Disable MOOSDB HTTP Server

   If not strictly required, disable the optional MOOSDB HTTP server module to eliminate the unauthenticated attack surface.

2. 2

   Network Segmentation

   Restrict access to MOOSDB HTTP ports to trusted internal networks only via firewall rules; never expose these ports to the public internet.

3. 3

   Implement Compensating Authentication

   Place the MOOSDB HTTP server behind a reverse proxy or VPN requiring authentication, since the underlying service lacks native auth controls.

4. 4

   Monitor and Alert

   Deploy network monitoring to detect and alert on unexpected HTTP traffic to MOOSDB ports or anomalous variable writes to actuator/override variables.

5. 5

   Upgrade When Patch Available

   Track upstream MOOS-IvP project for a patched release addressing this authentication bypass and upgrade as soon as available.

6. 6

   Validate Command Integrity

   For systems integrating autonomous decision-making agents with MOOSDB, implement independent validation/sanity checks on actuator commands before execution to detect injected or anomalous overrides.