CVE-2026-27007: OpenClaw's sandbox config hash sorted primitive arrays and suppressed needed container recreation
OpenClaw's sandbox config hash sorted arrays of plain values, so changing only the order of entries such as Docker `dns` or `binds` left the hash unchanged. OpenClaw then reused a stale sandbox container instead of recreating it. Versions up to 2026.2.14 are affected. Fixed in 2026.2.15.
Published Feb 18, 2026 · Updated Feb 20, 2026 · Analysis Nov 1, 2026
What an attacker can do
normalizeForHash in src/agents/sandbox/config-hash.ts recursively sorted any array holding only primitive values before hashing. OpenClaw compares this hash with the one for the running sandbox container to decide whether to recreate it. Two configs that differ only by array order produced the same hash, so a config change was treated as no change.
Order matters in some sandbox settings. The advisory names Docker dns and binds. For example, the order of DNS servers decides which resolver is tried first, and an order change in binds can alter which mount wins for an overlapping path. An operator who reorders them to tighten the sandbox sees no effect: the old container keeps running with the old settings.
This is an integrity issue with local, low-privilege access (4.8). It needs no attacker action by itself; it means a security change you made may not have been applied. It does not let an outsider escape the sandbox.
Who is affected
The openclaw npm package up to and including 2026.2.14. It affects deployments that use the OpenClaw sandbox and have edited the order of array settings such as Docker dns or binds, or the sandbox browser's binds, and expected a container rebuild. Check your version:
openclaw --versionopenclaw
- Ecosystem
- npm
- Affected
- < 2026.2.15
- Fixed in
- 2026.2.15
- Check
npm ls openclaw
How to fix it
Upgrade to openclaw 2026.2.15 or later.
npm install -g [email protected]Array order is now preserved when normalizing for the hash. Object keys are still sorted, so key order alone does not trigger a rebuild. After upgrading, containers created under the old hash may still carry stale settings from before an order-only change. Recreate your sandbox containers once so they match the current config.
How to tell if you were hit
Compare the live container's settings with your OpenClaw config. Inspect a running sandbox container to see its actual DNS servers and bind mounts, then check the order against your config file. Any mismatch after an order-only edit points to a reused stale container. Remove the container so OpenClaw recreates it.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Description
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.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
<=2026.2.14 - Patched (planned next release):
>=2026.2.15 - Latest published npm version at triage time (2026-02-16):
2026.2.14
Remediation
Array ordering is now preserved during hash normalization; only object key ordering remains normalized for deterministic hashing.
Fix Commit(s)
41ded303b4f6dae5afa854531ff837c3276ad60b
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.15) so after npm publish, the advisory can be published directly without reopening version metadata edits.
Thanks @kexinoh ( of Tencent zhuque Lab, by https://github.com/Tencent/AI-Infra-Guard) for reporting.
Credited to kexinoh.
Questions
- Can this let an attacker escape the sandbox?
The advisory describes it as a configuration integrity issue. Stale containers keep old settings; it describes no escape or remote access.
- Which settings are affected?
Order-sensitive primitive arrays, with Docker
dnsandbindsgiven as examples. The sandbox browserbindsalso had the problem, according to the fix's tests.- Do I need to recreate containers after upgrading?
Yes, as a precaution. The fix changes how future hashes are computed, but a container started under old settings is not rewritten by it.
- Which versions are affected?
Up to and including 2026.2.14. Version 2026.2.15 fixes it.
References
Read for this analysis:
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-62197
OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
medium8.5Oct 21, 2026CVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026
