openclaw
Affected
- introduced
0, fixed2026.2.22(semver)
Fixed versions
2026.2.22
Fix
- Fixed version
2026.2.22npm install [email protected]
Advisory
Also known as: CVE-2026-29607
OpenClaw's allow-always wrapper persistence could bypass future approvals and enable command execution
Summary
In openclaw npm releases up to and including 2026.2.21-2, approving wrapped system.run commands with allow-always in security=allowlist mode could persist wrapper-level allowlist entries and enable later approval-bypass execution of different inner payloads.
Affected Packages / Versions
openclaw (npm)<= 2026.2.21-22026.2.22Detailsallow-always persistence was based on wrapper-level resolution instead of stable inner executable intent. A benign approved wrapper invocation could therefore broaden future trust boundaries.
Affected paths included gateway and node-host execution approval persistence flows. The fix now persists inner executable paths for known dispatch-wrapper chains (env, nice, nohup, stdbuf, timeout) and fails closed when safe unwrapping cannot be derived.
Impact
Authorization boundary bypass in allowlist mode, potentially leading to approval-free command execution (RCE class) on subsequent wrapped invocations.
Mitigation
Upgrade to 2026.2.22 (planned next release) or run with stricter exec policy (ask=always / security=deny) until upgraded.
Fix Commit(s)
24c954d972400f508814532dea0e4dcb38418bb0Release Process Notepatched_versions is pre-set to 2026.2.22 so this advisory is publish-ready; publish after the npm release is live.
OpenClaw thanks @tdjackey for reporting.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.2.22 (semver)2026.2.22
2026.2.22npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0