# CVE-2026-85438: MOOS-IvP through 24.8.1 Out-of-Bounds Write via Unvalidated IvP Payload Counts

> Attackers can trigger memory corruption and potential code execution in MOOS-IvP by sending crafted IvP payloads with invalid dimension counts.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-fhxv-4m7f-gpmr

## What is CVE-2026-85438?

CVE-2026-85438 is a critical memory corruption vulnerability in moos-ivp, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MOOS-IvP through 24.8.1 contains a buffer overflow vulnerability in StringToIvPFunction() where dimension, piece, and degree counts from encoded BHV_IPF payloads are used as allocation sizes and loop bounds without validation. Attackers can supply crafted payloads with mismatched dimension values to write attacker-controlled doubles past the end of the IvPBox weight array, causing memory corruption and potential code execution.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Mit Moos-Ivp.

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

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

## Is CVE-2026-85438 being exploited?

There is no known exploitation of CVE-2026-85438 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-85429](https://insights.sbomify.com/CVE-2026-85429/): MOOS-IvP through 24.8.1 uFldNodeComms Node Message Source Spoofing (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85438 is a critical memory corruption vulnerability in moos-ivp, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85438 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-85438/ (Markdown: https://insights.sbomify.com/CVE-2026-85438/index.md)
```

## Sources

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

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