MOOS-IvP up to 24.8.1 SplitHandler handlePreCheckSplitDir dir os command injection

Summaryinfo

A vulnerability identified as critical has been detected in MOOS-IvP up to 24.8.1. Affected is the function SplitHandler::handlePreCheckSplitDir of the component SplitHandler. This manipulation of the argument dir causes os command injection. This vulnerability is tracked as CVE-2026-85439. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in MOOS-IvP up to 24.8.1. It has been declared as critical. Affected by this vulnerability is the function SplitHandler::handlePreCheckSplitDir of the component SplitHandler. The manipulation of the argument dir with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

MOOS-IvP through 24.8.1 contains a remote code execution vulnerability in alogsplit's SplitHandler::handlePreCheckSplitDir() function that fails to sanitize shell metacharacters in log file pathnames. Attackers can embed shell syntax in log file names or the --dir parameter to execute arbitrary commands with the privileges of the operator running alogsplit.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-85439 since 09/03/2026. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/04/2026). MITRE ATT&CK project uses the attack technique T1202 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• MOOS-IvP

Version

• 24.8.0
• 24.8.1

Website

• Product: https://github.com/moos-ivp/moos-ivp/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion