Is CVE-2026-85435 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-85435 being exploited in the wild.

How severe is CVE-2026-85435?

Critical severity, with a CVSS score of 9.1, published 3 September 2026.

Which products and versions are affected?

MOOS-IvP uFldNodeBroker through 24.8.1.

Is there a fix for CVE-2026-85435?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-85435 attacked?

It is attacked over the network.

Am I affected by CVE-2026-85435?

Check whether you run MOOS-IvP uFldNodeBroker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-85435: MOOS-IvP uFldNodeBroker message source validation bypass

CVE-2026-85435 · Severity: critical · CVSS 9.1 · Published 2026-09-03

MOOS-IvP is middleware used to control and coordinate autonomous marine vehicles. uFldNodeBroker is a critical component that routes messages between vehicles and shore-based systems. An attacker with network access to the vehicle's internal bus can publish fraudulent shore route enrollment messages, tricking the broker into forwarding sensitive vehicle data (sensor readings, control commands) to attacker-controlled endpoints, potentially causing vehicle malfunction or data theft.

Vendors: MOOS-IvP.

Quick answers

Is CVE-2026-85435 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-85435 being exploited in the wild.
How severe is CVE-2026-85435?: Critical severity, with a CVSS score of 9.1, published 3 September 2026.
Which products and versions are affected?: MOOS-IvP uFldNodeBroker through 24.8.1.
Is there a fix for CVE-2026-85435?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-85435 attacked?: It is attacked over the network.
Am I affected by CVE-2026-85435?: Check whether you run MOOS-IvP uFldNodeBroker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

MOOS-IvP uFldNodeBroker through version 24.8.1 fails to validate the source of TRY_SHORE_HOST messages on the vehicle communication bus. The vulnerability is a message source authentication bypass: the broker accepts shore route enrollment messages from any publisher without cryptographic or ACL-based verification of origin. An attacker with network access to the vehicle bus (local or via a compromised component) can publish malicious TRY_SHORE_HOST messages to enroll attacker-controlled shore routes. Once enrolled, the broker bridges all vehicle traffic—including sensor data and control information—to the attacker-controlled endpoint. No authentication or special privileges are required; the attack requires only network reachability to the vehicle bus. A patch addressing source validation is expected from the MOOS-IvP project.

Affected products

MOOS-IvP uFldNodeBroker through 24.8.1

Timeline

2026-09-03: disclosed: CVE-2026-85435 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.