CVE-2026-32018: 
OpenClaw (formerly Moltbot or Clawdbot) vulnerability analysis and mitigation

CVE-2026-32018 is a race condition vulnerability in OpenClaw (npm package) affecting versions prior to 2026.2.19. Concurrent updateRegistry and removeRegistryEntry operations for sandbox containers and browsers are performed without locking, enabling unsynchronized read-modify-write sequences that can corrupt sandbox state. The vulnerability was published on March 19, 2026, and assigned by VulnCheck. It carries a CVSS v3.1 base score of 4.8 (Medium) and a CVSS v4.0 base score of 2.0 (Low) (GitHub Advisory, VulnCheck).

The root cause is CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization / Race Condition). The updateRegistry and removeRegistryEntry functions in src/agents/sandbox/registry.ts perform read-modify-write operations on JSON registry files (containers.json, browsers.json) without any file locking or atomic replacement mechanism. When two operations execute concurrently — for example, a removeRegistryEntry and an updateRegistry for the same container — one operation can read a stale snapshot before the other completes its write, causing the later write to overwrite the earlier result. This can lead to lost updates, resurrection of deleted entries, or desynchronized sandbox state affecting sandbox list, sandbox prune, and sandbox recreate --all operations. The fix introduced shared file locks and atomic replacement to serialize these writes (GitHub Advisory, Fix Commit).

Successful exploitation can cause registry updates to lose data, resurrect previously removed sandbox container or browser entries, or corrupt the overall sandbox state. This primarily affects integrity and availability of sandbox management operations — specifically sandbox list, sandbox prune, and sandbox recreate --all — potentially causing containers or browsers to be incorrectly tracked, retained, or recreated. There is no confidentiality impact identified; the vulnerability does not expose sensitive data or enable privilege escalation (GitHub Advisory).

No public proof-of-concept exploit code or in-the-wild exploitation has been reported. The EPSS score is approximately 0.011% (0.000110), indicating very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires high attack complexity, as it depends on precise timing of concurrent operations, and the CVSS v4.0 vector requires local access with low privileges (VulnCheck).

1. Identify target: Confirm the target system is running OpenClaw (npm) version ≤ 2026.2.17 with sandbox container or browser management active.
2. Trigger concurrent operations: Initiate simultaneous updateRegistry and removeRegistryEntry calls targeting the same container or browser entry — for example, by spawning two concurrent processes or async tasks that each interact with the sandbox registry at the same time.
3. Race the read-modify-write window: Because neither operation holds a file lock, both read the current registry state (e.g., containers.json) before either writes back. The operation that writes last overwrites the other's changes.
4. Achieve corruption: Depending on timing, the result is either a lost update (a new container entry disappears) or a resurrected deleted entry (a removed container reappears in the registry).
5. Leverage desync: Use the corrupted registry state to interfere with sandbox list, sandbox prune, or sandbox recreate --all operations, potentially causing unintended container lifecycle actions (GitHub Advisory, Fix Commit).

• File System: Unexpected entries in containers.json or browsers.json (OpenClaw state directory) that were previously removed, or missing entries that should be present after recent updates.
• Logs: Anomalous output from sandbox list showing containers or browsers that were pruned or removed; unexpected behavior during sandbox prune or sandbox recreate --all (e.g., containers not being cleaned up or being recreated unexpectedly).
• Process: Multiple concurrent OpenClaw processes simultaneously writing to the sandbox registry files, observable via process monitoring tools (e.g., lsof, inotifywait on the state directory).

Upgrade OpenClaw (npm) to version 2026.2.19 or later, which serializes sandbox registry writes using shared file locks and atomic replacement to prevent race conditions. The fix was introduced in commit cc29be8c9 and is available as of the 2026.2.18/2026.2.19 release. No configuration-based workaround is documented; upgrading is the recommended and only reliable remediation (GitHub Advisory, Fix Commit).

The vulnerability was reported by security researcher @kexinoh and acknowledged by the OpenClaw maintainer (steipete) in the GitHub Security Advisory. No significant broader media coverage, vendor statements beyond the advisory, or notable community discussion has been identified for this moderate-severity issue.