Security readout for executives and security teams
Plain-English summary
OpenClaw can be tricked into running attacker-controlled code when it starts a shell for system.run. The flaw can bypass command allowlists through HOME and ZDOTDIR startup-file behavior. An attacker needs low privileges and exploitation is high complexity, but success can mean code execution in affected OpenClaw versions before 2026.2.22.
Executive priority
Treat this as a high-priority patching item for any OpenClaw deployment used in automation, operations, or security workflows. The issue can bypass command allowlists and lead to code execution, but current provided evidence does not show active exploitation.
Technical view
CVE-2026-32056 is a CWE-78 command injection issue in OpenClaw system.run. Unsanitized shell startup environment variables HOME and ZDOTDIR can cause attacker-controlled startup files to execute before allowlist-evaluated commands run. The bundled CVSS v4.0 score is 7.7 high, with network attack vector, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where OpenClaw before 2026.2.22 is deployed and untrusted or lower-privileged users can influence system.run inputs or its shell environment. The bundle does not identify specific downstream products, managed services, or default-exposed configurations.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. Exploitation appears to require control over relevant environment variables or startup-file locations, then abuse of shell initialization behavior before command allowlist checks occur. Do not assume internet-wide exploitation from the provided evidence.
Researcher notes
Focus review on system.run call paths, environment construction, privilege boundaries, and shell invocation behavior. Validate whether HOME and ZDOTDIR are sanitized or controlled after applying the patch. Evidence is limited to the provided advisory metadata, patch reference, CVE data, and VulnCheck entry.
Mitigation direction
- Upgrade OpenClaw to 2026.2.22 or later.
- Review the GitHub advisory and patch commit for vendor-confirmed remediation details.
- Restrict who can influence system.run inputs and execution environments until patched.
- Harden service execution contexts to reduce writable startup-file paths.
- Monitor vendor guidance for any follow-up fixes or configuration advice.
Validation and detection
- Inventory OpenClaw installations and record exact versions.
- Confirm affected deployments are running 2026.2.22 or later.
- Review use of system.run in application workflows and integrations.
- Check whether lower-privileged users can control shell environment variables.
- Review logs for unusual system.run failures or unexpected child-process behavior.
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-32056 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
- High
- CVSS
- 7.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
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:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.7HighVector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:H/PR:L/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
- GitHub Security Advisory (GHSA-xgf2-vxv2-rrmg)CVE reference, VulnCheck · vendor-advisory
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck Advisory: OpenClaw < 2026.2.22 - Remote Code Execution via Shell Startup Environment Variable Injection in system.runCVE 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.