OpenClaw versions prior to 2026.2.24 contain a command injection vulnerability in the system.run shell-wrapper that allows attackers to execute hidden commands by injecting positional argv carriers after inline shell payloads. Attackers can craft misleading approval text while executing arbitrary commands through trailing positional arguments that bypass display context validation.
Security readout for executives and security teams
Plain-English summary
OpenClaw before 2026.2.24 can show a misleading approval prompt while running different hidden commands. This is not described as wormable or unauthenticated, but it can let a low-privileged attacker cause high-impact integrity and availability damage if a user approves the action.
Executive priority
Treat this as a focused remediation item, not an emergency internet-wide incident. Prioritize patching where OpenClaw can execute operational commands or where approvals are handled by less technical users.
Technical view
The issue is command injection in OpenClaw's system.run shell-wrapper. Crafted trailing positional arguments can bypass display context validation after an inline shell payload, creating a mismatch between approval text and executed behavior. CVSS is 6.4 with low privileges and user interaction required.
Likely exposure
Exposure is likely limited to organizations running OpenClaw versions before 2026.2.24, especially where users approve shell-wrapper or agent-driven command execution. The provided sources do not identify hosted services, downstream products, or unauthenticated exposure.
Exploitation context
The bundle does not cite CISA KEV listing or active exploitation. Exploitation requires a crafted command approval scenario, prior low privilege access, high attack complexity, and user interaction. Impact is primarily integrity and availability, not confidentiality per the CVSS vector.
Researcher notes
Evidence supports command injection through approval-display confusion in the shell-wrapper. The bundle does not provide proof of exploitation in the wild, affected forks, detailed fixed-version notes beyond 2026.2.24, or compensating controls beyond upgrading and limiting access.
Mitigation direction
Upgrade OpenClaw to 2026.2.24 or later.
Review the GitHub advisory and patch commits for vendor-specific guidance.
Restrict shell-wrapper or system.run access until patched.
Limit approval authority to trusted users and workflows.
Review recent approvals for mismatched displayed intent and execution outcome.
Validation and detection
Inventory OpenClaw deployments and record exact versions.
Flag any OpenClaw version earlier than 2026.2.24.
Confirm whether system.run shell-wrapper functionality is enabled or reachable.
Check whether patch commits are present in deployed builds.
Review command approval logs for misleading or inconsistent approval text.
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 · low confidence lookup
CWE-436: 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.
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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-436 · source CWE mapping
Interpretation Conflict
Interpretation Conflict represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.