CVE-2026-34425
Shell-Bleed Bypass in OpenClaw Enables Arbitrary Script Execution
Publication date: 2026-04-02
Last updated on: 2026-04-15
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.4.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-184 | The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-34425 is a vulnerability in OpenClaw versions prior to commit 8aceaf5 that allows attackers to bypass the shell-bleed protection preflight validation. This happens because the validation mechanism fails to recognize complex or piped command forms such as piped execution, command substitution, or subshell invocation. As a result, attackers can craft commands that evade the validateScriptFileForShellBleed() checks and execute arbitrary script content that should have been blocked.
The root cause is an incomplete list of disallowed inputs (CWE-184), which leads to a fail-open condition in the exec script preflight mechanism, allowing unsafe scripts to run due to complex interpreter invocation patterns or malformed path inputs.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of CVE-2026-34425 on compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary script content on systems running vulnerable versions of OpenClaw by bypassing the script validation checks. This means unauthorized or unsafe scripts could run, potentially leading to unauthorized actions, data manipulation, or system compromise.
Because the vulnerability involves a fail-open bypass in the preflight validation, it weakens the defense-in-depth security mechanism designed to prevent unsafe script execution, increasing the risk of exploitation with low attack complexity and without requiring user interaction.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update OpenClaw to version 2026.4.2 or later, which includes the fix that closes the fail-open bypass in the exec script preflight validation.
The patch ensures that complex interpreter invocations and malformed script paths are properly validated and rejected if unsafe, preventing unauthorized script execution.
Applying this update will harden the shell-bleed protection mechanism and prevent attackers from bypassing script validation using piped or complex command forms.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves bypassing the shell-bleed protection in OpenClaw by using complex command forms such as piped execution, command substitution, or subshell invocation that the parser fails to recognize.
To detect exploitation attempts on your system or network, you should monitor for suspicious script executions that include piped commands, command substitutions (e.g., using backticks or $()), or subshell invocations that might bypass validation.
While no specific detection commands are provided in the available resources, you can use system auditing or logging tools to capture and analyze script execution patterns. For example, on Linux systems, you might use commands like:
- Audit script execution logs with commands such as `auditctl` to monitor execution of scripts or commands involving pipes or subshells.
- Use `ps` or `top` to look for running processes with suspicious command lines involving pipes or command substitutions.
- Search shell history files (e.g., `.bash_history`) for commands containing pipes (`|`), backticks (`` ` ``), or `$()` which might indicate attempts to exploit the vulnerability.
Additionally, ensure your OpenClaw installation is updated to version 2026.4.2 or later, which includes the fix for this vulnerability, to prevent exploitation.