OpenClaw before 2026.4.8 contains an approval-timeout fallback mechanism that bypasses strictInlineEval explicit-approval requirements on gateway and node exec hosts. Attackers can exploit this timeout fallback to execute inline eval commands that should require explicit user approval, circumventing the intended security boundary.
References
Configurations
History
30 Apr 2026, 14:04
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:* | |
| First Time |
Openclaw openclaw
Openclaw |
|
| References | () https://github.com/openclaw/openclaw/commit/d7c3210cd6f5fdfdc1beff4c9541673e814354d5 - Patch | |
| References | () https://github.com/openclaw/openclaw/security/advisories/GHSA-q2gc-xjqw-qp89 - Vendor Advisory | |
| References | () https://www.vulncheck.com/advisories/openclaw-strictinlineeval-approval-boundary-bypass-via-approval-timeout-fallback - Third Party Advisory |
28 Apr 2026, 19:37
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-04-28 19:37
Updated : 2026-04-30 14:04
NVD link : CVE-2026-42423
Mitre link : CVE-2026-42423
CVE.ORG link : CVE-2026-42423
JSON object : View
Products Affected
openclaw
- openclaw
CWE
CWE-636
Not Failing Securely ('Failing Open')
