OpenClaw version 2026.2.22 prior to 2026.2.23 contains an arbitrary code execution vulnerability in shell-env that allows attackers to execute attacker-controlled binaries by exploiting trusted-prefix fallback logic for the $SHELL variable. An attacker can influence the $SHELL environment variable on systems with writable trusted-prefix directories such as /opt/homebrew/bin to execute arbitrary binaries in the OpenClaw process context.
Security readout for executives and security teams
Plain-English summary
OpenClaw 2026.2.22 can trust the SHELL environment variable in a way that may run the wrong binary. A local, low-privileged attacker who can influence that environment and place files in a trusted-prefix directory could execute code inside the OpenClaw process.
Executive priority
Treat this as a targeted local integrity risk, not a confirmed mass-exploitation emergency. Prioritize upgrading any 2026.2.22 deployments, especially shared developer workstations, build hosts, or systems where local users can modify trusted-prefix paths.
Technical view
The issue is arbitrary binary execution in OpenClaw shell-env trusted-prefix fallback handling for SHELL. The cited CVSS vector is local, low complexity, low privilege, no user interaction, with high integrity impact and low availability impact. Sources identify 2026.2.22 as affected and 2026.2.23 as patched.
Likely exposure
Exposure appears limited to OpenClaw 2026.2.22 systems where an attacker can influence SHELL and write into trusted-prefix directories such as /opt/homebrew/bin. The source bundle lists other versions as unaffected by default.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. The attack requires local access with low privileges and a writable trusted-prefix path, so internet-wide remote exploitation is not supported by the evidence.
Researcher notes
This maps to CWE-829 and depends on unsafe trust in externally controlled functionality. Focus validation on version presence, environment inheritance boundaries, and writable trusted-prefix directories. Do not assume broader OpenClaw versions or active exploitation without additional vendor or KEV evidence.
Mitigation direction
Upgrade OpenClaw deployments running 2026.2.22 to 2026.2.23 or later.
Review the vendor advisory and patch notes before broad rollout.
Restrict write access to trusted-prefix directories used by OpenClaw hosts.
Harden service launch environments so untrusted users cannot control SHELL.
Monitor vendor guidance for any revised affected-version or mitigation details.
Validation and detection
Inventory OpenClaw installations and confirm whether version 2026.2.22 is present.
Verify upgraded systems report OpenClaw 2026.2.23 or later.
Review host permissions on trusted-prefix directories such as /opt/homebrew/bin.
Confirm OpenClaw services do not inherit untrusted SHELL values.
Check security monitoring for unexpected OpenClaw child-process activity.
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-829: 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-829 · source CWE mapping
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.