Quick answers
- Is CVE-2026-85434 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85434 being exploited in the wild.
- How severe is CVE-2026-85434?
- Critical severity, with a CVSS score of 9.1, published 3 September 2026.
- Which products and versions are affected?
- MOOS-IvP through 24.8.1.
- Is there a fix for CVE-2026-85434?
- 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-85434 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85434?
- Check whether you run MOOS-IvP 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
The vulnerability is an authentication bypass in uFldShoreBroker's handling of NODE_BROKER_PING messages. The broker creates outbound bridge routes based on HostRecord data in these pings without verifying the sender's identity or the message authenticity. An unauthenticated network attacker can craft and publish a NODE_BROKER_PING message with malicious HostRecord fields to redirect variables that should be bridged to one node toward an attacker-controlled address instead. No user interaction or prior authentication is required—the attack is triggered upon message receipt. This allows interception, manipulation, or poisoning of bridged data streams, potentially enabling command injection into autonomous vehicle systems.
Affected products
- MOOS-IvP MOOS-IvP through 24.8.1
Timeline
- 2026-09-03: disclosed