External risk intelligence

MOOS-IvP uFldShoreBroker Bridge Route Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-85434

MOOS-IvP is a specialized software suite used for autonomous marine vehicle research and control. Components like uFldShoreBroker operate within isolated, domain-specific networks for inter-vehicle communication and coordination, not as public-facing internet services or common enterprise web applications.

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

A vulnerability in the MOOS-IvP software's uFldShoreBroker component allows attackers to potentially redirect bridged variables by sending forged network messages. This could lead to the manipulation of communication routes within systems using this technology.

Unverified messages can hijack communication routes.
Critical for specialized autonomous systems.
Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted network messages to redirect critical system information. This could allow them to manipulate how different parts of the system communicate, potentially leading to unauthorized control or data alteration.

Attacker sends malicious network messages.
Vulnerable component creates unverified routes.
Risk of data redirection and manipulation.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to manipulate communication between MOOS-IvP components, redirecting critical data or control signals by impersonating legitimate network nodes. This is possible when the affected uFldShoreBroker is configured to accept unverified node pings.

Bridged variables could be redirected.
Attackers can publish forged ping messages.
Control signals may be compromised.

Operational Fix

Recommended remediation, mitigation, and detection steps

The MOOS-IvP uFldShoreBroker component's failure to authenticate node ping messages requires immediate attention from teams managing autonomous marine vehicle systems. The first practical step is to identify all instances of uFldShoreBroker, determine their network reachability and criticality, and locate the responsible system owner to plan remediation.

Platform and application owners should lead remediation.
Verify unauthenticated NODE_BROKER_PING message exposure.
Coordinate system updates with vendor.

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 the MOOS-IvP software used for?

MOOS-IvP is an open-source set of software tools designed for autonomous marine robotics. Researchers and engineers use it to control and coordinate the behavior of unmanned underwater and surface vehicles. The uFldShoreBroker component, specifically, acts as a communication hub that bridges information between these vehicles and shore-based systems, ensuring that telemetry and control signals are shared within the autonomous network.

What kind of vulnerability is CVE-2026-85434?

This vulnerability is classified as CWE-345: Insufficient Verification of Data Authenticity. In plain language, the software fails to confirm that a network message is truly coming from a trusted vehicle. Because it trusts any incoming ping, an attacker can fake the identity of a node, tricking the broker into accepting instructions that redirect where critical data flows.

How does an attacker trigger this bug?

An attacker triggers the vulnerability by sending a malicious NODE_BROKER_PING message to the uFldShoreBroker. This message contains forged HostRecord information designed to deceive the broker. The issue does not occur when the broker receives legitimate, authenticated traffic, but because the software currently lacks an internal verification step, it cannot distinguish between valid vehicle pings and those injected by an unauthorized party.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal indicates that exploitation is very unlikely for most users. Because MOOS-IvP is specialized for autonomous marine research, its components typically operate within isolated, domain-specific networks rather than being exposed to the public internet like standard web servers. Your primary risk exists if your specific implementation bridges these autonomous networks to broader, less secure environments.

What steps should I take to address this issue?

First, conduct an inventory to locate all active instances of the uFldShoreBroker component within your autonomous fleet infrastructure. Identify which systems have network paths that could receive untrusted pings. Once you have identified these assets, coordinate with your technical team to apply the necessary software updates from the MOOS-IvP project to ensure that all node communication is properly authenticated before bridge routes are established.

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.