An environment variable injection vulnerability in OpenClaw allows local attackers to override sensitive runtime configurations, potentially leading to a total compromise of the application state.

This flaw exists because the application loads a local .env file from the current working directory before applying trusted configuration settings. An unauthenticated attacker who can influence the local environment can inject malicious configuration values that govern the application behavior.

The ability to inject environment variables provides an attacker with significant control over the application runtime, which may lead to unauthorized data access or complete system takeover. With a CVSS score of 8.6, this vulnerability represents a high risk to business operations, as it could facilitate the bypass of security controls and integrity protections.

Immediate Action: Update the OpenClaw package to version 2026.3.28 or later, as provided by the official NPM repository.

Proactive Monitoring: Audit workspaces and project directories for the presence of unauthorized or unexpected .env files. Additionally, monitor system logs for unusual configuration initialization patterns during startup.

Compensating Controls: Ensure that the application is executed from a secure, read-only directory whenever possible to prevent the placement of malicious configuration files. Restricting user permissions on the file system can also mitigate the risk of an attacker successfully injecting a local .env file.

Public Exploit Available: Unknown.

Given the potential for high-impact configuration overrides, organizations should prioritize updating to the patched version of OpenClaw. Organizations should verify that all development and production environments have applied the 2026.3.28 update to effectively eliminate the injection vector.