Cyber & AI intelligence
Wasteland.
Briefs indexed2403
Issues26
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-85425 2026-09-03

CVE-2026-85425: Command Injection in MOOS-IvP iSay Speech Handler

"A critical (CVSS 9.8) remote code execution flaw in MOOS-IvP's iSay module lets unauthenticated attackers run arbitrary shell commands by publishing crafted `SAY_MOOS` messages."

A critical (CVSS 9.8) remote code execution flaw in MOOS-IvP's iSay module lets unauthenticated attackers run arbitrary shell commands by publishing crafted SAY_MOOS messages.

What Is It

CVE-2026-85425 is an OS command injection vulnerability (CWE-78) in the iSay component of MOOS-IvP, the open-source autonomy middleware used for marine and unmanned vehicle robotics. The SAY_MOOS variable handler passes unsanitized text directly to a shell command. An attacker who can publish SAY_MOOS messages containing backticks or command-substitution syntax executes arbitrary commands as the iSay process user.

The flaw was disclosed by VulnCheck and carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), along with a CVSS 4.0 score of 9.3. The vulnerable code path is in ivp/src/iSay/Sayer.cpp.

Why It Matters

Every exploitability metric is at its worst case: network attack vector, low complexity, no privileges required, and no user interaction. Impact is high across confidentiality, integrity, and availability; full compromise of the process context.

In MOOS architectures, any client able to publish to the MOOS database can reach the vulnerable handler, so an attacker positioned on the autonomy network gets code execution on the vehicle or shoreside machine running iSay. The record was published 2026-09-03 and remains in Received status at NVD.

What's Vulnerable

Patch Status

An upstream fix exists. Commit ed3a441 and pull request #120 in the moos-ivp repository address the injection. Operators running 24.8.1 or earlier should update to a build containing that commit. Where patching is not immediately possible, restricting who can publish to the MOOS database limits reachability of the handler.

No CISA KEV entry was supplied for this CVE, so there is no confirmed active exploitation or federal remediation deadline at this time.

Sources