CVE-2026-27007 in OpenClaw
Summary
by MITRE • 02/20/2026
OpenClaw is a personal AI assistant. Prior to version 2026.2.15, `normalizeForHash` in `src/agents/sandbox/config-hash.ts` recursively sorted arrays that contained only primitive values. This made order-sensitive sandbox configuration arrays hash to the same value even when order changed. In OpenClaw sandbox flows, this hash is used to decide whether existing sandbox containers should be recreated. As a result, order-only config changes (for example Docker `dns` and `binds` array order) could be treated as unchanged and stale containers could be reused. This is a configuration integrity issue affecting sandbox recreation behavior. Starting in version 2026.2.15, array ordering is preserved during hash normalization; only object key ordering remains normalized for deterministic hashing.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 02/22/2026
The vulnerability described in CVE-2026-27007 affects OpenClaw, a personal AI assistant platform, specifically targeting the sandbox configuration hashing mechanism that governs container recreation decisions. This issue stems from a flaw in the `normalizeForHash` function located in `src/agents/sandbox/config-hash.ts` where arrays containing only primitive values were being recursively sorted during hash computation. The fundamental problem lies in the assumption that array order is irrelevant for configuration integrity, which creates a dangerous false positive scenario where different array orders produce identical hash values. This behavior directly violates the principle of deterministic hashing that should preserve configuration state changes, creating a configuration integrity issue that undermines the security and reliability of the sandbox environment.
The technical implementation flaw manifests when the system processes sandbox configuration arrays such as Docker `dns` and `binds` parameters where ordering is semantically significant. When these arrays are sorted during hash normalization, legitimate configuration changes that depend on element order are effectively masked, causing the system to incorrectly determine that no changes have occurred. This misclassification leads to stale sandbox containers being reused instead of creating new ones with updated configurations, creating a persistent security risk where outdated container states may continue to operate with potentially compromised or outdated settings. The vulnerability specifically impacts the decision-making process for sandbox recreation, where the hash value serves as the primary indicator for determining whether existing containers should be destroyed and recreated with new configurations.
The operational impact of this vulnerability extends beyond simple configuration management to potentially compromise the integrity of the entire sandboxed execution environment. When order-sensitive configurations are treated as equivalent due to improper hash normalization, attackers could exploit this behavior to maintain persistent access through stale containers or to bypass security controls that depend on fresh container initialization. This issue affects the core security model of OpenClaw's sandboxing mechanism, potentially allowing for privilege escalation or persistent execution of malicious code within the sandboxed environment. The vulnerability represents a configuration integrity failure that could enable attackers to manipulate the sandbox lifecycle management process, undermining the fundamental security assumptions of container isolation and fresh execution states.
The fix implemented in version 2026.2.15 addresses the core issue by preserving array ordering during hash normalization while maintaining object key ordering normalization for deterministic behavior. This approach aligns with security best practices for configuration management and follows the principle of least privilege by ensuring that only semantically significant configuration changes trigger container recreation. The solution maintains deterministic hashing for object structures while preserving the semantic meaning of array order, preventing the false equivalence that previously allowed stale configurations to persist. This remediation directly addresses the CWE-1037 weakness related to configuration management and aligns with ATT&CK techniques that involve privilege escalation through container manipulation, ensuring that configuration changes are properly detected and acted upon. The fix represents a balanced approach to maintaining system reliability while addressing the security implications of improper hash normalization that could otherwise allow persistent security violations.