CVE-2026-85429Public exploitNetwork attack vector

Arbitrary notifications via spoofed node identity

Published Sep 3, 2026 · Updated Sep 5, 2026

Source-identity spoofing in MOOS-IvP uFldNodeComms 24.8.1 and earlier allows remote attackers to post arbitrary variable notifications. FldNodeComms::handleMailNodeMessage() trusts src_node from each NODE_MESSAGE body, so range, staleness, and group checks use the claimed node's ledger entry before uFldMessageHandler posts the named variable without an allowlist. Any field publisher that can reach the MOOSDB path can impersonate another node and alter mission-control variables, including deploy, return, abort, or manual-override state.

CVSS severity8.7
High
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Source-identity spoofing in MOOS-IvP uFldNodeComms 24.8.1 and earlier allows remote attackers to post arbitrary variable notifications. FldNodeComms::handleMailNodeMessage() trusts src_node from each NODE_MESSAGE body, so range, staleness, and group checks use the claimed node's ledger entry before uFldMessageHandler posts the named variable without an allowlist. Any field publisher that can reach the MOOSDB path can impersonate another node and alter mission-control variables, including deploy, return, abort, or manual-override state.

The record

CVE
CVE-2026-85429
Published
Sep 3, 2026
Updated
Sep 5, 2026
Vendor
MOOS-IvP
Product
MOOS-IvP
Classifications
CWE-345, T1565.002
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 3, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=24.8.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

MOOS-IvP · MOOS-IvPversion=0 <=24.8.1

Published CVSS scores

7.5VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
8.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-345Insufficient Verification of Data Authenticity
T1565.002Transmitted Data Manipulation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo