Disclosed weakness · no CVE recorded
OpenClaw allowed sandbox state to block Gateway restart and configuration reload
OpenClaw · OpenClaw · Gateway readiness
First documented disclosure · Review checkpoint
Summary
Sandbox-owned workspace state could prevent the shared Gateway from reloading configuration or restarting.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The upstream sources document the behavior and correction. They 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
The readiness check treated state controlled by a sandbox as evidence of a pending operator migration.
Conditions required
A sandbox can write its own workspace and the Gateway subsequently reloads or restarts.
Potential impact
Agents and channels that rely on the Gateway could lose service.
Affected versions and configurations
The upstream report identifies the affected behavior without specifying a complete version range.
Fix and mitigation status
The 2026.11.4 stable release includes this issue-specific correction.
Practical next steps
Deploy the correction and use operator-owned state to diagnose readiness failures.
Operating lesson
Keep process-wide availability decisions outside the trust boundary of individual workloads.
Evidence and limits
The reported impact is availability. The source does not establish privilege elevation.
Sources
- OpenClaw · fix(workspace): keep sandbox-written files out of Gateway readiness
Primary source ·
- OpenClaw 2026.11.4 stable release notes
Primary source ·