Quick answers
- Is CVE-2026-85426 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85426 being exploited in the wild.
- How severe is CVE-2026-85426?
- Critical severity, with a CVSS score of 9.8, published 3 September 2026.
- Which products and versions are affected?
- MOOS-IvP uMemWatch through 24.8.1.
- Is there a fix for CVE-2026-85426?
- 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-85426 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85426?
- Check whether you run MOOS-IvP uMemWatch 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 shell command injection flaw in uMemWatch (versions through 24.8.1) where attacker-supplied MOOS client names are used to construct shell commands without proper sanitization. The vulnerable code in MemWatch.cpp passes unquoted client names directly to system calls, allowing injection of shell metacharacters. No authentication is required; an attacker needs only network access to the MOOS middleware to register a malicious client name. Successful exploitation results in arbitrary command execution as the uMemWatch process user. A fix would involve proper quoting or escaping of client names before passing them to shell commands, or preferring direct APIs that do not invoke a shell.
Affected products
- MOOS-IvP uMemWatch through 24.8.1
Timeline
- 2026-09-03: disclosed