Earlier OpenClaw releases used SHA‑1 to hash sandbox identifier cache keys for Docker and browser sandbox configurations. Because SHA‑1 is susceptible to collision attacks, an adversary can craft distinct sandbox identifiers that generate the same hash. This allows one sandbox configuration to be misinterpreted as another, resulting in cache poisoning and the reuse of an unsafe sandbox state. The weakness corresponds to CWE‑327, reflecting the use of a deprecated cryptographic algorithm.

The affected product is OpenClaw from the vendor OpenClaw. All versions prior to 2026.2.15 are vulnerable; this includes any deployment using those historical releases of OpenClaw's node.js based implementation.

The CVSS base score is 8.7, indicating high confidentiality and integrity impact. The EPSS score is below 1%, suggesting that real‑world exploitation attempts are currently rare. The vulnerability is not listed in the CISA KEV catalog. Attackers would likely need to forge sandbox identifiers that collide on the SHA‑1 hash; the likely attack vector is a remote manipulation of sandbox configuration data, as inferred from the description, since no local privilege is required to insert such identifiers.