OpenClaw Vulnerability: Workspace .env File Can Inject Runtime-Control Variables

openclaw Updated 18 Apr 2026

Summary

17/04/2026

Disclosed on

MODERATE

Severity

Yes i

Fix available

Moderate

Severity

6.8

CVSS Score

GHSA-7wv4-cc7p-jhxc: OpenClaw: Workspace .env could inject OpenClaw runtime-control variables. Affects openclaw versions < 2026.4.9. Fixed in 2026.4.9. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

OpenClaw is an open-source package designed for managing and controlling various runtime aspects of applications. It allows users to configure settings such as update sources, gateway URLs, and browser executable paths through environment variables. However, a recent vulnerability has been identified that allows malicious .env files to manipulate these runtime-control variables, potentially leading to unauthorized behavior in applications using OpenClaw.

Vulnerability Detail

The vulnerability arises from the ability of a malicious workspace .env file to inject OpenClaw runtime-control variables. This can affect critical configurations such as update sources and gateway URLs, leading to potential security risks and unintended application behavior. The issue is rooted in the way OpenClaw loads environment variables, which did not adequately restrict certain keys and key families from being set through the .env file.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.4.9

This is the first release that contains the fix.

npm install openclaw@2026.4.9

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a workaround, users should ensure that their workspace does not contain any malicious .env files that could set harmful runtime-control variables. Regularly auditing and validating the contents of .env files can help mitigate risks until the package is updated.

Conclusion

The OpenClaw vulnerability related to the workspace .env file poses a significant risk by allowing the injection of runtime-control variables. Users are strongly advised to update to version 2026.4.9 or later to mitigate this risk. Regular audits of environment files and using tools like Vulert can further enhance security.

See every vulnerability recorded for openclaw →