GHSA-736r-jwj6-4w23

GHSA-736r-jwj6-4w23 HIGH
Published April 17, 2026

## 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...

Full CISO analysis pending enrichment.

Affected Systems

Package Ecosystem Vulnerable Range Patched
openclaw npm >= 2026.4.5, < 2026.4.10 2026.4.10
2 dependents 92% patched ~1d to patch Full package profile →

Do you use openclaw? You're affected.

Severity & Risk

CVSS 3.1
N/A
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
N/A

Recommended Action

Patch available

Update openclaw to version 2026.4.10

Compliance Impact

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is GHSA-736r-jwj6-4w23?

OpenClaw: Sandboxed agents could escape exec routing via host=node override

Is GHSA-736r-jwj6-4w23 actively exploited?

No confirmed active exploitation of GHSA-736r-jwj6-4w23 has been reported, but organizations should still patch proactively.

How to fix GHSA-736r-jwj6-4w23?

Update to patched version: openclaw 2026.4.10.

What is the CVSS score for GHSA-736r-jwj6-4w23?

No CVSS score has been assigned yet.

Technical Details

NVD Description

## 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 `openclaw@2026.4.14` 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.

Timeline

Published
April 17, 2026
Last Modified
April 17, 2026
First Seen
April 18, 2026

Related Vulnerabilities