Quick answers
- Is CVE-2026-85429 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85429 being exploited in the wild.
- How severe is CVE-2026-85429?
- High severity, with a CVSS score of 7.5, published 3 September 2026.
- Which products and versions are affected?
- MOOS-IvP uFldNodeComms through 24.8.1.
- Is there a fix for CVE-2026-85429?
- 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-85429 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85429?
- Check whether you run MOOS-IvP uFldNodeComms 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 a lack of source identity validation in uFldNodeComms. The component trusts the source node identity contained within the message body of NODE_MESSAGE packets rather than validating it against the actual network connection source. An attacker with network access can craft malicious NODE_MESSAGE packets with forged source identities and post arbitrary variable notifications without proper authentication, allowing impersonation of legitimate nodes and unauthorized command injection.
Affected products
- MOOS-IvP uFldNodeComms through 24.8.1
Timeline
- 2026-09-03: disclosed