OpenClaw’s sandbox configuration hashing routine previously sorted arrays of only primitive values before generating a hash. Because the order of such arrays was lost, sandbox configurations that differed only in sequence produced identical hash values. The hash is used to decide whether a sandbox container needs to be recreated. As a result, changes that altered only the order of items (such as Docker dns or binds lists) were treated as unchanged, so containers that were still running stale configurations were reused. This flaw allows an attacker who can inject or modify sandbox configuration to cause the system to continue using unintended settings, thereby compromising configuration integrity.

All installations of OpenClaw running any version before 2026.2.15 are affected. The vendor is OpenClaw, product OpenClaw, and the issue is present until the 2026.2.15 release which restores array ordering during hashing.

The vulnerability has a CVSS score of 4.8, indicating moderate severity, and an EPSS score of less than 1 %, suggesting very low likelihood of exploitation in the wild. It is not listed in the CISA KEV catalog. The attack vector is inferred to be local or internal, requiring the ability to alter sandbox configuration data; an attacker who can change the order of configuration arrays can force the system to continue using stale containers. While the impact is limited to configuration integrity, the effect may lead to the execution of outdated or insecure sandbox instances.