Quick answers
- Is CVE-2026-85445 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85445 being exploited in the wild.
- How severe is CVE-2026-85445?
- High severity, with a CVSS score of 7.5, published 3 September 2026.
- Which products and versions are affected?
- MOOS-IvP through 24.8.1.
- Is there a fix for CVE-2026-85445?
- 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-85445 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85445?
- Check whether you run MOOS-IvP 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 exists in the Demuxer::addMuxPacket() function, which fails to validate the packet count value declared in multiplexed message headers before allocating memory. An attacker can send a malformed mux packet declaring an arbitrarily large packet count, causing the function to attempt unbounded memory allocation that exhausts system resources. This is a memory exhaustion denial of service attack requiring network access to the affected MOOS-IvP service. The vulnerability affects MOOS-IvP through version 24.8.1 and can be exploited without authentication or user interaction.
Affected products
- MOOS-IvP MOOS-IvP through 24.8.1
Timeline
- 2026-09-03: disclosed