N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-gq83-8q7q-9hfx

GHSA-gq83-8q7q-9hfx: OpenClaw's serialize sandbox registry writes to prevent races and delete-rollback corruption

Impact

Concurrent updateRegistry/removeRegistryEntry operations for sandbox containers and browsers could lose updates or resurrect removed entries under race conditions.

The registry writes were read-modify-write in a window with no locking and permissive fallback parsing, so concurrent registry updates could produce stale snapshots and overwrite each other.

That desyncs sandbox state and can affect sandbox list, sandbox prune, and sandbox recreate --all behavior.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.17
Patched versions: 2026.2.18

Fix Commit(s)

cc29be8c9

OpenClaw thanks @kexinoh for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-gq83-8q7q-9hfx

GHSA-gq83-8q7q-9hfx:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.2.19	2026.2.19

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a classic race condition (CWE-362) where shared resources (the containers.json and browsers.json registry files) are modified without proper synchronization. The vulnerability description explicitly mentions that "Concurrent updateRegistry/removeRegistryEntry operations...could lose updates or resurrect removed entries under race conditions."

The analysis of the patch cc29be8c9 confirms this. The core change is the introduction of a locking mechanism (withRegistryLock) around the read-modify-write logic in four functions: updateRegistry, removeRegistryEntry, updateBrowserRegistry, and removeBrowserRegistryEntry.

Before the patch, these functions would read the entire registry file, modify their in-memory representation, and then write the entire file back to disk. If two processes did this at the same time, the process that writes last would overwrite the changes of the first, leading to data loss or inconsistency. For example, if one process adds an entry and another removes a different entry, the final state of the registry would depend on which process finished writing last, potentially losing one of the two changes.

The vulnerable functions are precisely these four exported functions from src/agents/sandbox/registry.ts, as they are the entry points for modifying the sandbox and browser registries. Any runtime profile or stack trace captured during the problematic concurrent operations would show calls to these functions. The patch also introduces atomic file writes (write-to-temp-and-rename) to prevent corruption from partial writes, further hardening the registry operations.

Vulnerable functions

updateRegistry

src/agents/sandbox/registry.ts

This function performs a read-modify-write operation on the sandbox registry file without any locking. If multiple instances of this function or `removeRegistryEntry` are executed concurrently, a race condition can occur, leading to lost updates or data corruption. The patch fixes this by wrapping the operation in a lock (`withRegistryLock`).

removeRegistryEntry

src/agents/sandbox/registry.ts

This function reads the sandbox registry, removes an entry, and writes the result back. This read-modify-write operation is not atomic and lacks synchronization, making it vulnerable to race conditions when run concurrently with other registry modification functions like `updateRegistry`. This can lead to data corruption, such as resurrecting a deleted entry if another update writes a stale copy of the registry back to disk. The patch introduces a lock to serialize access.

updateBrowserRegistry

src/agents/sandbox/registry.ts

Similar to `updateRegistry`, this function performs an unsynchronized read-modify-write operation on the browser registry file. Concurrent execution can lead to a race condition, causing updates to be lost. The patch addresses this by adding a lock (`withRegistryLock`) to ensure atomic updates.

removeBrowserRegistryEntry

src/agents/sandbox/registry.ts

This function is vulnerable to a race condition for the same reasons as `removeRegistryEntry`. It performs a non-atomic read-modify-write operation on the browser registry file, which can result in data corruption if executed concurrently with other registry write operations. The patch mitigates this by serializing access with a lock.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.