CVE-2026-32910
Approval Bypass in OpenClaw system.run Enables Executable Rebinding
Publication date: 2026-03-23
Last updated on: 2026-03-23
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.3.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-426 | The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions before 2026.3.1 and involves an approval bypass in the system.run function. Specifically, when the first argument (argv[0]) is not path-like, the system fails to correctly bind the executable's identity. This flaw allows an attacker to rebind the executable after it has been approved, meaning they can modify the PATH resolution to execute a different binary than the one originally approved by the operator.
How can this vulnerability impact me? :
The impact of this vulnerability is significant because it allows an attacker with limited privileges to bypass the approval process and execute unauthorized code. By modifying the PATH resolution after approval, the attacker can run a different binary than intended, potentially leading to unauthorized actions, data compromise, or system integrity issues.
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?
I don't know