Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
4.8
OpenClaw: Stale Sandboxes Reused Due to Config Order Change
CVE-2026-27007
GHSA-xxvh-5hwj-42pp
Summary
OpenClaw, a sandboxing tool, has a bug where it mistakenly treats order changes in configuration arrays as no changes. This can lead to old sandbox containers being reused, which can cause issues. To fix this, the developers have changed how they handle array order in configuration hashes, so updates to the tool will ensure that order matters and old containers are properly recreated.
What to do
- Update steipete openclaw to version 2026.2.15.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| steipete | openclaw | <= 2026.2.15 | 2026.2.15 |
| openclaw | openclaw | <= 2026.2.15 | – |
Original title
OpenClaw's sandbox config hash sorted primitive arrays and suppressed needed container recreation
Original description
## 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.
`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.
nvd CVSS3.1
3.3
nvd CVSS4.0
4.8
Vulnerability type
CWE-1254
- https://github.com/openclaw/openclaw/releases/tag/v2026.2.15 Product Release Notes
- https://github.com/openclaw/openclaw/security/advisories/GHSA-xxvh-5hwj-42pp Vendor Advisory Patch
- https://nvd.nist.gov/vuln/detail/CVE-2026-27007
- https://github.com/advisories/GHSA-xxvh-5hwj-42pp
- https://github.com/openclaw/openclaw/commit/41ded303b4f6dae5afa854531ff837c3276a... Patch
Published: 18 Feb 2026 · Updated: 11 Mar 2026 · First seen: 6 Mar 2026