Skip to content
IoT

CVE-2026-85435

CRITICAL
Critical
EPSS 0.17%Patch availableSep 4, 2026

Unauthenticated shore-route enrollment in MOOS-IvP allows interception/control of vehicle traffic.

common questions

Is CVE-2026-85435 being exploited?

Not confirmed. CVE-2026-85435 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.17% probability of exploitation in the next 30 days.

How severe is CVE-2026-85435?

CVE-2026-85435 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-85435?

Yes. A fix has been recorded for CVE-2026-85435. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-85435 affect?

CVE-2026-85435 affects MOOS-IvP uFldNodeBroker <= 24.8.1, Autonomous marine vehicles using MOOS-IvP, Vehicle communication bridges/vehicle bus. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-85435?

Upgrade to patched MOOS-IvP or apply commit d66394f; restrict publisher access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MOOS-IvP uFldNodeBroker <= 24.8.1Autonomous marine vehicles using MOOS-IvPVehicle communication bridges/vehicle bus
impact

Unauthenticated publishers can enroll attacker-controlled shore routes to receive bridged vehicle sensor and control data, enabling eavesdropping and potential remote control.

action required

Immediate action required

affected versions
moos-ivp moos-ivp
  • affected<= 24.8.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free