GHSA-xxvh-5hwj-42pp — openclaw
Fix: openclaw/openclaw@41ded30GHSA-xxvh-5hwj-42pp is a CWE-1254 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw's sandbox config hash sorted primitive arrays and suppressed needed container recreation
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xxvh-5hwj-42pp.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.15npm install openclaw@2026.2.15 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xxvh-5hwj-42pp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xxvh-5hwj-42pp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xxvh-5hwj-42pp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xxvh-5hwj-42pp in your dependencies?
O3 Security finds GHSA-xxvh-5hwj-42pp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.