OpenClaw: Sandboxed agents could escape exec routing via host=node overrideGHSA-736r-jwj6-4w23
HIGHFix: openclaw/openclaw#63880GHSA-736r-jwj6-4w23 is a high-severity (CVSS 8.8) CWE-863 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-736r-jwj6-4w23.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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
Summary
Sandboxed agents could escape exec routing via host=node override.
Affected Packages / Versions
- Package:
openclaw - Ecosystem: npm
- Affected versions:
>= 2026.4.5 < 2026.4.10 - Patched versions:
>= 2026.4.10
Impact
A sandboxed agent could request host: "node" and route exec to a remote node instead of the intended sandbox execution path, bypassing the sandbox routing boundary.
Technical Details
The fix blocks sandboxed exec escape to remote node targets and keeps routing aligned with the active sandbox policy.
Fix
The issue was fixed in #63880. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.
Fix Commit(s)
dffad08529202edbf34e4808788e1182fe10f6a9- PR: #63880
Release Process Note
Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.
Credits
Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | ≥ 2026.4.5&&< 2026.4.10 | 2026.4.10npm install openclaw@2026.4.10 |
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.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-736r-jwj6-4w23 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-736r-jwj6-4w23 in your dependencies?
Find it across npm, including transitive dependencies.