# CVE-2026-85439: MOOS-IvP through 24.8.1 alogsplit Command Injection via Input Pathname

> Attackers can execute arbitrary commands by injecting shell metacharacters into log file pathnames or the --dir parameter in alogsplit.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 5 Sep 2026
- **Also known as:** GHSA-fm2r-qmc4-5wf2

## What is CVE-2026-85439?

CVE-2026-85439 is a high-severity command injection vulnerability in moos-ivp, published on 3 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-85439?

It affects 1 product.


Products: Mit Moos-Ivp.

## How do I fix CVE-2026-85439?

No fix has been published for CVE-2026-85439 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85439 being exploited?

There is no known exploitation of CVE-2026-85439 in the wild and no public exploit code.

## Other vulnerabilities in moos-ivp

- [CVE-2026-85425](https://insights.sbomify.com/CVE-2026-85425/): MOOS-IvP through 24.8.1 iSay Command Injection via SAY_MOOS (critical 9.3)
- [CVE-2026-85434](https://insights.sbomify.com/CVE-2026-85434/): MOOS-IvP through 24.8.1 uFldShoreBroker Bridge Route Injection via Unverified Node Ping (critical 9.3)
- [CVE-2026-85435](https://insights.sbomify.com/CVE-2026-85435/): MOOS-IvP through 24.8.1 uFldNodeBroker Unauthenticated Shore Route Enrollment (critical 9.3)
- [CVE-2026-85437](https://insights.sbomify.com/CVE-2026-85437/): MOOS-IvP through 24.8.1 Buffer Overflow in IvP Function String Decoders (critical 9.3)
- [CVE-2026-85438](https://insights.sbomify.com/CVE-2026-85438/): MOOS-IvP through 24.8.1 Out-of-Bounds Write via Unvalidated IvP Payload Counts (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85439 and fix it if it is affected.

What it is: CVE-2026-85439 is a high-severity command injection vulnerability in moos-ivp, published on 3 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-85439 in the wild and no public exploit code.

Affected product: moos-ivp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85439/ (Markdown: https://insights.sbomify.com/CVE-2026-85439/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85439
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85439
- OSV: https://osv.dev/vulnerability/CVE-2026-85439

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85439/
Summaries are generated and may contain mistakes; the official description above is the record.