CVE-2026-27566
Allowlist Bypass in OpenClaw system.run Enables Command Execution
Publication date: 2026-03-19
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.22 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2026-27566 is an allowlist bypass vulnerability in OpenClaw versions prior to 2026.2.22 affecting the system.run exec function. The vulnerability occurs because the allowlist analysis fails to properly unwrap chains of environment and shell-dispatch wrapper binaries, such as 'env' and 'bash'. Attackers can exploit this by routing execution through these wrappers to smuggle payloads that appear to satisfy allowlist entries but actually execute commands not included in the allowlist."}, {'type': 'paragraph', 'content': 'The root cause is that the system.run function treats wrapper binaries as the effective executable without fully resolving nested wrappers, allowing unauthorized commands to bypass allowlist checks. The fix involves enhancing the command resolution logic to transparently unwrap these wrappers and apply allowlist policies to the actual commands executed.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability allows attackers who can trigger system.run requests under an allowlist policy to bypass intended allowlist restrictions. By smuggling unauthorized commands through environment or shell wrapper binaries, attackers can execute commands not permitted by the allowlist.
The impact is a high-severity security risk involving OS Command Injection, enabling attackers with limited privileges to execute unauthorized commands, potentially compromising system integrity and security.
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': 'Detection of this vulnerability involves identifying attempts to execute commands through wrapper binaries such as env or shell dispatchers (bash, sh, zsh, etc.) that bypass the allowlist checks.'}, {'type': 'paragraph', 'content': 'You can monitor system logs or command execution logs for suspicious usage of wrapper commands that include environment variable assignments or shell command flags like -c, -lc, or --command.'}, {'type': 'list_item', 'content': "Use command-line tools to search for executions involving env wrappers, for example: `ps aux | grep '\\benv\\b'` to find running processes using env."}, {'type': 'list_item', 'content': "Check for shell commands executed with inline commands, e.g., `ps aux | grep -E 'bash -c|sh -c|zsh -c'`."}, {'type': 'list_item', 'content': 'Audit logs or system.run invocation logs for commands that include chains of wrappers or environment variable assignments preceding the actual command.'}, {'type': 'paragraph', 'content': 'Since the vulnerability involves smuggling payloads through wrapper binaries, detection requires analyzing the effective commands behind wrappers rather than just the wrapper binaries themselves.'}] [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade OpenClaw to version 2026.2.22 or later, where the vulnerability is fixed by enhancing the command resolution logic to unwrap environment and shell dispatch wrappers properly.
This fix ensures that allowlist policies are applied to the actual executed commands rather than the wrapper binaries, preventing bypasses.
Until the upgrade is applied, consider restricting or monitoring the use of wrapper binaries like env, bash, sh, zsh, and powershell in system.run calls or other execution contexts.
Implement additional logging and alerting on suspicious command execution patterns involving wrapper chains.