Quick answers
- Is CVE-2026-85430 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85430 being exploited in the wild.
- How severe is CVE-2026-85430?
- Critical severity, with a CVSS score of 9.1, published 3 September 2026.
- Which products and versions are affected?
- MOOS Essential-Moos through 10.0.1.
- Is there a fix for CVE-2026-85430?
- 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-85430 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-85430?
- Check whether you run MOOS Essential-Moos 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 an authentication bypass in pShare's UDP listener (Listener.cpp). The listener accepts and republishes UDP datagrams from any source without validating the sender's identity or legitimacy, preserving the attacker-claimed identity in the message. The root cause is missing source authentication and validation on incoming UDP datagrams. An attacker with network access to the pShare listening port can send crafted datagrams to inject spoofed messages into the MOOS community, or send malformed packets to trigger a process crash. No patch information is currently available in the advisory. The attack requires network reachability to the pShare UDP listener port; no authentication is required.
Affected products
- MOOS essential-moos through 10.0.1
Timeline
- 2026-09-03: disclosed