# CVE-2026-85444: MOOS-IvP through 24.8.1 Out-of-Bounds Read in isBraced, isQuoted and isChevroned

> Attackers can trigger out-of-bounds reads in MOOS-IvP via crafted NODE_REPORT messages, potentially accessing adjacent memory or causing crashes.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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:** 5 Sep 2026
- **Also known as:** GHSA-3g44-rh7h-p3w2

## What is CVE-2026-85444?

CVE-2026-85444 is a high-severity 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 over-read vulnerability in isQuoted(), isBraced(), and isChevroned() functions that strip whitespace but index using the original string length. Attackers can send NODE_REPORT messages with leading or trailing whitespace to read past buffer bounds and access adjacent memory.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Mit Moos-Ivp.

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

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

## Is CVE-2026-85444 being exploited?

There is no known exploitation of CVE-2026-85444 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-85444 and fix it if it is affected.

What it is: CVE-2026-85444 is a high-severity 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-85444 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-85444/ (Markdown: https://insights.sbomify.com/CVE-2026-85444/index.md)
```

## Sources

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

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