CVE-2026-32065
Approval-Integrity Bypass in OpenClaw system.run Enables Command Execution
Publication date: 2026-03-21
Last updated on: 2026-03-24
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.25 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-436 | Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-32065 is an approval-integrity bypass vulnerability in OpenClaw versions prior to 2026.2.25 affecting the system.run command execution process.
The vulnerability occurs because OpenClaw uses the rendered command text, which trims whitespace from argv tokens, as the approval identity, but at runtime executes the raw argv without trimming. This mismatch allows an attacker to craft a trailing-space executable token that appears benign to the approver but causes execution of a different binary than displayed.
If an attacker can influence the command argv and reuse or obtain a matching approval context, they can execute unexpected commands under the OpenClaw runtime user, effectively bypassing the intended approval mechanism.
This issue is categorized under CWE-436 (Interpretation Conflict) and CWE-863 (Incorrect Authorization), indicating incorrect authorization checks due to differing input handling.
How can this vulnerability impact me? :
This vulnerability can lead to unexpected command execution under the OpenClaw runtime user if an attacker can influence the command arguments and reuse an approval context.
An attacker could exploit the mismatch between approved command display and actual execution to run unauthorized binaries or commands, potentially compromising system integrity or security.
Because the approval mechanism can be bypassed, this may allow privilege escalation or unauthorized actions within the environment where OpenClaw is deployed.
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?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability CVE-2026-32065, you should upgrade OpenClaw to version 2026.2.25 or later, where the issue has been fixed.
The fix binds execution approvals to the exact argument vector (argv) identity rather than just the command string, preventing approval reuse attacks involving trailing spaces or subtle differences in executable paths.
Ensure that your deployment does not rely on multi-user sharing of a single gateway host or configuration as a security boundary, since this vulnerability exploits approval context reuse.