Critical 9.1Published Sep 3, 2026

CVE-2026-85435MOOS-IvP through 24.8.1 uFldNodeBroker Unauthenticated Shore Route Enrollment

Updated under an hour ago (Oct 28, 2026, 1:00 PM ET)

Does this affect you?

It affects moos-ivp and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for moos-ivp

Exploited in the last 30 days

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.

CVSS: 9.1 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE): CWE-345
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: VulnCheck
NVD analysis: Analyzed
Record last updated: Sep 4, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

moos-ivp moos-ivp moos_ivp:moos_ivp (from the name)	through 24.8.1	CNA record
mit moos-ivp mit:moos-ivp	before 24.8.1	NVD

References

References

https://github.com/moos-ivp/moos-ivp/pull/124	issue-tracking, patch
https://github.com/moos-ivp/moos-ivp/commit/d66394f576cae0c63c0a777760e1595802b83edf	patch, issue-tracking
https://github.com/moos-ivp/moos-ivp	product
https://github.com/moos-ivp/moos-ivp/blob/1de9ae146cd63c209e8c3fd81611a4ed2472971b/ivp/src/uFldNodeBroker/NodeBroker.cpp#L97	technical-description, issue-tracking, patch
https://www.vulncheck.com/advisories/moos-ivp-through-24.8.1-ufldnodebroker-unauthenticated-shore-route-enrollment	third-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.