Security readout for executives and security teams
Plain-English summary
MOOS-IvP iSay can treat specially crafted SAY_MOOS text as operating-system commands. A remote attacker able to publish that variable could run commands with iSay’s account, potentially stealing data, changing systems, or disrupting operations. The supplied record rates this 9.8 critical.
Executive priority
Prioritize immediate exposure assessment and containment. Internet-facing, broadly connected, or operationally sensitive deployments warrant emergency handling because compromise could affect confidentiality, integrity, and availability. Systems without active iSay or untrusted publishing paths are lower priority but still require documented validation.
Technical view
Through version 24.8.1, iSay’s SAY_MOOS handler passes unsanitized text into a shell command, creating CWE-78 command injection. The stated attack requires no privileges or user interaction and executes with the iSay process user’s permissions. A corrective commit exists in an unmerged pull request.
Likely exposure
Exposure is most likely where iSay through 24.8.1 is running and an untrusted or compromised participant can publish SAY_MOOS messages. Impact depends on the iSay account’s permissions and reachable resources. The supplied affected-product metadata is internally inconsistent, so inventories require manual confirmation.
Exploitation context
The bundle establishes a remotely reachable command-injection path and provides a verified code sink. It does not establish observed exploitation, and the CVE is not identified as being in KEV. Treat it as readily exploitable in exposed configurations without claiming active attacks.
Researcher notes
The vulnerable sink is identified in Sayer.cpp, and the proposed change is associated with pull request 120. Because that pull request is described as unmerged, it should not be represented as a released vendor fix. The affected array’s version “0” and default-unaffected status conflict with the narrative claim covering releases through 24.8.1.
Mitigation direction
- Restrict SAY_MOOS publishing to explicitly trusted systems and identities.
- Segment or block untrusted network access to affected MOOS communities.
- Disable iSay where it is unnecessary until authoritative remediation is available.
- Minimize the iSay process account’s privileges and accessible resources.
- Review vendor guidance and the unmerged pull request before applying any code change.
Validation and detection
- Inventory MOOS-IvP and iSay deployments, recording exact versions and operating contexts.
- Confirm whether iSay is active and subscribes to SAY_MOOS.
- Identify every identity and network path capable of publishing SAY_MOOS messages.
- Review iSay-host telemetry for unexpected child processes or shell activity.
- Verify compensating controls prevent untrusted SAY_MOOS publication.
- Confirm any remediation is vendor-approved and survives regression testing.
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-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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-85425 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 #120CVE 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
- Sayer.cpp (verified sink)CVE reference, VulnCheck · technical-description
- VulnCheck Advisory: MOOS-IvP through 24.8.1 iSay Command Injection via SAY_MOOSCVE 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.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.