LiveActive security incident?Get immediate response
CVE Record

CVE-2026-85426: MOOS-IvP through 24.8.1 uMemWatch Command Injection via MOOS Client Names

MOOS-IvP uMemWatch through 24.8.1 constructs shell commands from attacker-chosen MOOS client names without sanitization. Attackers can inject shell metacharacters into client names to execute arbitrary commands as the uMemWatch process user through unquoted redirection targets in system calls.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

MOOS-IvP uMemWatch through 24.8.1 may let an unauthenticated network attacker turn a malicious MOOS client name into operating-system commands. Successful exploitation could compromise data, alter operations, or stop the affected process with the privileges of the uMemWatch account.

Executive priority

Treat reachable production deployments as an urgent remediation priority because compromise could affect confidentiality, integrity, and availability. Immediately reduce untrusted access, establish ownership, and track vendor remediation. Prioritize systems supporting safety-sensitive, autonomous, or operational environments.

Technical view

uMemWatch incorporates attacker-controlled MOOS client names into shell commands without adequate sanitization or quoting. Shell metacharacters can therefore alter commands executed through system calls, including commands containing unquoted redirection targets. The issue is classified as CWE-78 and scored CVSS 3.1 9.8.

Likely exposure

Exposure is most likely where uMemWatch through 24.8.1 is running and untrusted systems can register attacker-chosen MOOS client names. Actual reachability depends on deployment-specific network controls and MOOS access restrictions, which the supplied sources do not describe.

Exploitation context

The CVSS vector describes remote, low-complexity exploitation requiring neither privileges nor user interaction. The supplied record is not marked as KEV and provides no evidence of active exploitation. A proposed fix exists, but the referenced pull request was identified as unmerged.

Researcher notes

The cited source code and proposed change support the command-injection finding. However, the supplied structured affected entry lists version "0" with default status "unaffected," conflicting with the description of versions through 24.8.1. Confirm precise affected-version boundaries with the vendor before final fleet-wide conclusions.

Mitigation direction

  • Identify systems running MOOS-IvP uMemWatch through version 24.8.1.
  • Restrict MOOS connectivity and client registration to trusted systems wherever operationally feasible.
  • Disable uMemWatch where unnecessary, following operational safety and availability procedures.
  • Monitor Pull Request #121 and vendor guidance for an approved fix or fixed release.
  • Do not treat the unmerged commit as a supported production patch without vendor validation.

Validation and detection

  • Confirm installed MOOS-IvP versions and whether uMemWatch is enabled or running.
  • Map which networks and identities can register MOOS clients with affected deployments.
  • Review process execution and security logs for unexpected commands associated with uMemWatch.
  • Verify deployed mitigations prevent untrusted clients from supplying client names.
  • After vendor remediation, safely confirm malformed client names are rejected without shell execution.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2026-85426 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

2CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheck
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-85426Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
moos-ivpmoos-ivp0unaffected
Weakness

CWE details

CWE-78

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

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.

Open CWE intelligenceSame-CWE CVEs