CVE-2026-22175
Execution Approval Bypass in OpenClaw Allowlist via Shell Wrappers
Publication date: 2026-03-18
Last updated on: 2026-03-19
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.23 (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?
[{'type': 'paragraph', 'content': 'CVE-2026-22175 is a vulnerability in OpenClaw versions prior to 2026.2.23 that allows attackers to bypass execution approval controls in allowlist mode.'}, {'type': 'paragraph', 'content': "The issue arises because OpenClaw fails to properly recognize certain shell multiplexer wrappers like busybox and toybox when they invoke shell commands using 'sh -c'. This incomplete filtering (CWE-184) means that attackers can wrap arbitrary payloads inside these multiplexers, which then satisfy the stored allowlist rules incorrectly."}, {'type': 'paragraph', 'content': 'As a result, attackers can execute unauthorized commands despite the presence of execution approval restrictions, effectively bypassing the intended security controls.'}] [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized execution of arbitrary commands on systems using vulnerable versions of OpenClaw.
Because the allowlist mechanism can be bypassed via unrecognized shell multiplexers, attackers with limited privileges may escalate their capabilities or execute malicious payloads that should have been blocked.
This undermines the security posture of the system by allowing execution of potentially harmful commands, increasing the risk of compromise, data loss, or further exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability involves bypassing execution approval in OpenClaw by using unrecognized multiplexer shell wrappers such as busybox and toybox with sh -c commands. Detection involves monitoring for execution attempts that use these multiplexers to invoke shell commands, which may bypass allowlist rules.'}, {'type': 'paragraph', 'content': 'To detect potential exploitation attempts, you can look for processes or commands invoking busybox or toybox with sh -c wrappers that are not normally allowed or expected in your environment.'}, {'type': 'list_item', 'content': "Use commands like `ps aux | grep -E '(busybox|toybox) sh -c'` to identify running processes using these multiplexers with shell commands."}, {'type': 'list_item', 'content': 'Check your OpenClaw logs or audit logs for execution attempts involving busybox or toybox wrappers that bypass allowlist rules.'}, {'type': 'list_item', 'content': 'Monitor for unusual or unauthorized shell command executions wrapped by busybox or toybox using system monitoring or intrusion detection tools.'}] [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation is to upgrade OpenClaw to version 2026.2.23 or later, where this vulnerability has been fixed by properly recognizing and unwrapping shell multiplexer wrappers like busybox and toybox.
Until the upgrade is applied, you should consider restricting or monitoring the use of busybox and toybox shell wrappers on your systems to prevent attackers from exploiting the bypass.
- Apply the official patch or upgrade OpenClaw to version 2026.2.23 or newer.
- Implement stricter execution policies or monitoring for multiplexer shell wrappers such as busybox and toybox.
- Review and tighten allowlist rules to detect and block suspicious invocations involving shell multiplexers.