OpenClaw before 2026.3.11 contains an approval-integrity vulnerability in node-host system.run approvals that displays extracted shell payloads instead of the executed argv. Attackers can place wrapper binaries and induce wrapper-shaped commands to execute local code after operators approve misleading command text.
Security readout for executives and security teams
Plain-English summary
OpenClaw could show operators one command for approval while a different wrapper-driven command is actually executed. This creates a trust failure in approval workflows: a user may approve misleading text and unintentionally allow local code execution. The issue affects OpenClaw before 2026.3.11.
Executive priority
Treat this as high priority where OpenClaw is used for operational command execution. The main business risk is mistaken human approval leading to unintended local code execution. Prioritize upgrade and approval-log review, especially on systems with privileged operational workflows.
Technical view
The flaw is an approval-integrity UI mismatch in OpenClaw node-host system.run approvals. The approval interface displays extracted shell payloads rather than the executed argv. With low privileges and operator approval, an attacker can use wrapper binaries and wrapper-shaped commands to run unintended local code. CVSS v4 score is 7.3 high; CWE-451 is assigned.
Likely exposure
Organizations using OpenClaw node-host system.run approvals on versions before 2026.3.11 are the likely exposed population. Systems not using OpenClaw, already on 2026.3.11 or later, or without this approval workflow are not identified as affected in the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires low privileges and user approval, but the approval text can be misleading. Attack complexity is rated high, so this is serious but not described as broadly automated.
Researcher notes
Evidence is limited to the supplied CVE, GitHub advisory, and VulnCheck advisory metadata. The key research point is approval display integrity: extracted shell payloads differ from executed argv. Do not assume public exploitation or additional affected products without new source evidence.
Mitigation direction
Upgrade OpenClaw to 2026.3.11 or later.
Review the GitHub and VulnCheck advisories for vendor-specific guidance.
Restrict node-host system.run approvals to trusted operators until upgraded.
Audit recent approvals for wrapper-shaped commands or unexpected local binary execution.
Validation and detection
Inventory OpenClaw deployments and record exact versions.
Identify systems using node-host system.run approval workflows.
Confirm affected deployments are before 2026.3.11.
Compare approval records with executed argv where logs support it.
After upgrade, verify the displayed approval matches executed command details.
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-451: 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.
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
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-451 · source CWE mapping
User Interface (UI) Misrepresentation of Critical Information
User Interface (UI) Misrepresentation of Critical Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.