Security readout for executives and security teams
Plain-English summary
MOOS-IvP through 24.8.1 may mishandle maliciously encoded IvP function strings, corrupting memory and potentially allowing code execution. Systems processing attacker-controlled MOOS variables or alog files face the greatest risk. The supplied sources identify a proposed fix, but state that its pull request is not merged.
Executive priority
Treat this as an urgent remediation and exposure-reduction item for reachable or operationally sensitive MOOS-IvP deployments. Immediately restrict untrusted inputs, inventory affected installations, and monitor upstream resolution. Do not declare systems patched solely because an unmerged commit exists.
Technical view
IvP function string decoders trust declared field lengths without confirming sufficient input or destination capacity. Mismatched lengths can cause heap or stack buffer overflows, classified as CWE-787. The supplied CVSS 3.1 score is 9.8, reflecting network-accessible, low-complexity exploitation without privileges or user interaction and potentially complete confidentiality, integrity, and availability impact.
Likely exposure
Prioritize deployments running MOOS-IvP 24.8.1 or earlier that accept IvP function strings from untrusted MOOS variables or process untrusted alog files. Exposure is lower where inputs are authenticated, isolated, and strictly controlled. The bundle's structured affected-version entry is inconsistent with its description, so confirm installed versions and applicability with vendor guidance.
Exploitation context
The supplied record describes potential remote code execution, but provides no evidence of exploitation in the wild, and KEV is false. Treat malicious MOOS-variable input and imported alog files as plausible delivery paths. Actual exploit reliability, public proof-of-concept availability, and internet-wide exposure are not established by the bundle.
Researcher notes
The reported sink is FunctionEncoder.cpp, and the proposed change is commit 81ca795fcfd62b42002d277f5a2390f4c8ab8c7f under pull request 125. Review decoder length validation and all equivalent parsing paths. The bundle does not establish exploitability on every platform or configuration, and its affected-version metadata conflicts with the narrative range.
Mitigation direction
- Check upstream guidance and release history for a merged, supported fix before upgrading.
- Do not treat the unmerged proposed-fix commit as a supported release without vendor confirmation.
- Restrict MOOS variable publishers to authenticated, trusted systems and limit network reachability.
- Reject or quarantine alog files from untrusted sources until remediation is confirmed.
- Isolate affected processes and apply least privilege to reduce code-execution impact.
Validation and detection
- Inventory MOOS-IvP installations and record exact versions, build commits, and deployment roles.
- Identify components that decode IvP function strings from MOOS variables or alog files.
- Trace whether untrusted users, networks, or files can reach those decoding paths.
- Verify any remediation contains the referenced bounds-validation changes and is vendor-supported.
- Review crashes and memory-safety alerts associated with IvP function decoding.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-85437 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: 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
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Pull Request #125CVE reference, VulnCheck · issue-tracking, patch
- Proposed fix commit (pull request not merged)CVE reference, VulnCheck · patch
- https://github.com/moos-ivp/moos-ivpCVE reference, VulnCheck · product
- FunctionEncoder.cpp (verified sink)CVE reference, VulnCheck · technical-description
- VulnCheck Advisory: MOOS-IvP through 24.8.1 Buffer Overflow in IvP Function String DecodersCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.