An environment variable namespace collision vulnerability in OpenClaw before 2026.4.20 allows local attackers with user interaction to manipulate runtime behavior and achieve total system compromise.

This flaw involves an incomplete list of disallowed inputs, specifically failing to reserve the OPENCLAW_ runtime-control environment namespace in workspace dotenv files. The attacker requires local access and user interaction to trigger the condition with no initial privileges.

A successful exploit allows malicious workspaces to set variables such as OPENCLAW_GIT_DIR, manipulating trusted runtime behavior during source update or installer flows. This results in total technical impact, potentially leading to complete host compromise, unauthorized data access, and significant system downtime. While the CVSS score is 7.8, the severity reflects high confidentiality, integrity, and availability impacts on the local system.

Immediate Action: Update the OpenClaw package to version 2026.4.20 or later using the npm package manager.

Proactive Monitoring: Monitor local system access logs and environment variable configurations for anomalous changes during workspace loading or installer flows.

Compensating Controls: Restrict workspace creation and execution permissions to trusted users only, and audit all workspace configuration files for unauthorized dotenv overrides.

Public Exploit Available: No - As of May 7, 2026, there is no confirmed public exploit in the available data.

Organizations utilizing OpenClaw must treat this vulnerability with high priority due to its total technical impact on compromised systems. Administrators should apply the update to version 2026.4.20 immediately and enforce strict workspace access controls to prevent local manipulation attempts.