Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-85428 – Unauthenticated Actuator/Variable Write via MOOSDB HTTP Server – MOOS core-moos ≤ 1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-85428 is a missing authentication vulnerability (CWE-306) in the optional HTTP server built into MOOSDB, the message-passing database at the core of the MOOS (Mission Oriented Operating Suite) middleware used in robotics and autonomous vehicle (e.g., marine/underwater vehicle) systems. The HTTP interface accepts requests to "poke" (write) MOOS variables — including actuator and override commands — without requiring any credentials. The issue is rated CRITICAL (CVSS v3.1 9.8 / CVSS v4.0 9.3) because it allows any network-reachable, unauthenticated attacker to directly manipulate the control variables of a running MOOS-based system.

Technical details

  • Root cause: The MOOSDB HTTP server’s request handler (HandlePoke() in HTTPConnection.cpp, part of Core/libMOOS/DB/) parses VariableToPoke and NewValue parameters from incoming HTTP requests and writes the value directly into the MOOS database via Notify(), with no authentication, authorization, or access-control check performed anywhere in the request path.
  • Trigger conditions: The vulnerability is exploitable whenever the optional MOOSDB HTTP server component is enabled and reachable over the network (its default listening interface/port exposes this functionality).
  • Attack vector: Network — remote, unauthenticated attackers can send a simple crafted HTTP request specifying the target variable name and new value.
  • Impact: Because MOOS variables can represent actuator commands and safety overrides in robotic/autonomous platforms, successful exploitation allows an attacker to alter system state and potentially issue unauthorized actuator or override commands, impacting confidentiality, integrity, and availability of the controlled system.

Affected software

  • Vendor/Project: themoos
  • Product: core-moos
  • Affected versions: All versions through 10.4.0 (versions 0 – 10.4.0)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • CVSS v3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • (An accompanying CVSS v4.0 score of 9.3, Critical, is also published: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)

Mitigation and recommended actions

  • Immediate: Apply the upstream fix merged via pull request #77 to the themoos/core-moos repository (commit 7e3aecdbf5fe47980ea9399340c77940991a6fa5), which adds an authentication check to the HTTPConnection write/poke path. Upgrade to a version of core-moos that includes this fix once a formal release is available.
  • If patching is not immediately possible:
    • Disable the optional MOOSDB HTTP server component if it is not required for operations.
    • Restrict network access to the MOOSDB HTTP server/port to trusted hosts only (e.g., via firewall rules, network segmentation, or binding to localhost/internal management networks) so it is never reachable from untrusted or internet-facing networks.
    • Monitor for unexpected HTTP requests containing VariableToPoke/NewValue parameters against MOOSDB-hosting systems as an indicator of exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge