External risk intelligence

MOOS-IvP iSay Command Injection Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-85425

MOOS-IvP is a specialized open-source software suite designed for autonomous marine vehicle operations and research, not for public-facing internet services. It typically operates within isolated or local network environments for robot communication and control, making public internet exposure of the iSay process highly unlikely in standard deployments.

OS Command Injection

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

The MOOS-IvP iSay component has a critical vulnerability allowing remote code execution if an attacker can send specially crafted messages. This could potentially enable unauthorized command execution on affected systems.

Unsanitized text allows attackers to run commands.
Critical vulnerability could allow unauthorized command execution.
Confirm relevance and exposure of the affected technology.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this by publishing specially crafted messages to the MOOS messaging system, targeting the iSay component. Because the SAY_MOOS variable handler does not properly sanitize input before passing it to a shell command, an attacker can inject malicious commands using backticks or command substitution. This allows them to run arbitrary code on the system as the iSay process user, potentially leading to a complete compromise of the affected application.

Entry condition: Network access to the MOOS messaging system.
Trigger point: Publishing a SAY_MOOS message with crafted input.
Resulting risk: Arbitrary command execution.

Live Threat

Current exploitation, exposure, and threat context

An attacker could execute arbitrary commands on systems running affected versions of MOOS-IvP iSay. This is possible when an attacker can publish specially crafted SAY_MOOS messages, allowing them to inject commands through the SAY_MOOS variable handler which passes unsanitized text to a shell command.

System commands and process execution.
Publishing malicious SAY_MOOS messages.
Unauthorized arbitrary command execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

The MOOS-IvP iSay component's vulnerability in the SAY_MOOS variable handler likely impacts teams responsible for the operation and maintenance of autonomous marine vehicle systems. System owners or platform teams should first confirm the presence and reachability of affected iSay instances within their operational network. Subsequently, an assessment of business criticality and an accountable owner's identification are necessary to prioritize and plan remediation efforts.

Ownership: Platform or system owners.
Verify: System reachability and criticality.
Action: Plan remediation with accountable owners.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is MOOS-IvP iSay?

MOOS-IvP is an open-source software suite primarily used for coordinating autonomous marine vehicles and robotics research. The iSay component acts as a utility within this ecosystem, designed to handle audio or text announcements by passing messages through the system. It functions as a communication interface for these specialized robotic platforms.

What does the CVE-2026-85425 vulnerability mean?

This is an OS Command Injection vulnerability, categorized as CWE-78. It means the iSay component takes input from the system's messaging channel and runs it directly through a command shell without checking it first. If the input contains specific characters like backticks, the shell interprets those characters as instructions rather than plain text, allowing unauthorized code to execute.

How can an attacker trigger this vulnerability?

An attacker must be able to publish a specially crafted message to the MOOS messaging system that the iSay component processes. The vulnerability is triggered when the SAY_MOOS variable handler receives this text and passes it to a shell command. It is important to note that simply sending data that does not utilize command substitution syntax, such as backticks, will not trigger this specific command injection behavior.

Why should I care about this for my infrastructure?

According to Halo Surface Signal, this software is generally used in isolated or local environments for robot control, making direct internet exposure highly unlikely. However, if your specific network configuration allows untrusted parties to send messages to your MOOS-IvP messaging bus, your systems are at risk. You should care if your deployment connects to broader networks where unauthorized users could access the messaging interface.

Is there a first step for managing this risk?

Your first step is to identify where iSay is running within your robotic or marine vehicle networks. Once located, verify if the messaging interface is reachable by anything other than authorized, trusted controllers. You should treat this as a priority for platform teams to ensure that no unauthorized users can communicate with the messaging bus until the software is updated or secured.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.