Disclosed weakness · no CVE recorded

OpenClaw could select a workspace program when launching a child process

OpenClaw · OpenClaw CLI child-process startup

First documented disclosure · Review checkpoint

Summary

Workspace-controlled environment settings could place a local executable directory in the search path inherited by child processes.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The project documented the defect and its repair. The reviewed sources identify no malicious use.

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

CLI startup treated certain workspace-contained executable roots as trusted tool directories.

Conditions required

The CLI starts in a workspace that influences how it resolves external programs, and a child process requests a matching program.

Potential impact

A local program could run with the permissions of the OpenClaw process.

Affected versions and configurations

The project has not published a complete affected version range.

Fix and mitigation status

OpenClaw 2026.11.2 includes the fix. The exact first fixed release across all release lines is unverified.

Practical next steps

Update OpenClaw and keep trusted executable directories outside workspaces that supply untrusted content.

Operating lesson

Resolve child-process programs from directories the workspace cannot redefine.

Evidence and limits

The maintainer documents checks with controlled marker programs. The report does not establish remote execution against users or a complete release range.

Sources