MOOS-IvP through 24.8.1 uFldNodeBroker Unauthenticated Shore Route Enrollment
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-345.
Summary
MOOS-IvP uFldNodeBroker through 24.8.1 fails to validate the source of TRY_SHORE_HOST messages on the vehicle bus, allowing any publisher to enroll attacker-controlled shore routes. Attackers can publish malicious shore route messages to receive bridged vehicle traffic including sensor data and control information.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-85435
- 2026-10-03 Alias added: GHSA-7674-4w38-m6r3
References
More Moos-ivp vulnerabilities
- TI-2026-58623 MOOS-IvP through 24.8.1 iSay Command Injection via SAY_MOOS CVSS 4.0CRITICAL 9.3
- TI-2026-58635 MOOS-IvP through 24.8.1 Buffer Overflow in IvP Function String Decoders CVSS 4.0CRITICAL 9.3
- TI-2026-58636 MOOS-IvP through 24.8.1 Out-of-Bounds Write via Unvalidated IvP Payload Counts CVSS 4.0CRITICAL 9.3
- TI-2026-58632 MOOS-IvP through 24.8.1 uFldShoreBroker Bridge Route Injection via Unverified Node Ping CVSS 4.0CRITICAL 9.3
- TI-2026-58647 MOOS-IvP through 24.8.1 pMarineViewer Unbounded Memory Consumption via NODE_REPORT CVSS 4.0HIGH 8.7
- TI-2026-58646 MOOS-IvP through 24.8.1 uFldShoreBroker Unbounded Community State Retention CVSS 4.0HIGH 8.7
Sources
- CVE-2026-85435 · CVE Program
- CVE-2026-85435 · NVD
- FIRST EPSS
- GHSA-7674-4w38-m6r3 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences