OpenClaw up to 2026.2.23 positional interpretation conflict
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenClaw up to 2026.2.23. It has been rated as problematic. Affected by this issue is some unknown functionality. This manipulation of the argument positional causes interpretation conflict. This vulnerability is tracked as CVE-2026-32052. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability was found in OpenClaw up to 2026.2.23. It has been declared as problematic. Affected by this vulnerability is an unknown function. The manipulation of the argument positional with an unknown input leads to a interpretation conflict vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity, and availability. The summary by CVE is:
OpenClaw versions prior to 2026.2.24 contain a command injection vulnerability in the system.run shell-wrapper that allows attackers to execute hidden commands by injecting positional argv carriers after inline shell payloads. Attackers can craft misleading approval text while executing arbitrary commands through trailing positional arguments that bypass display context validation.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-32052 since 03/10/2026. The exploitation appears to be difficult. The attack can be launched remotely. Technical details are known, but no exploit is available.
Upgrading to version 2026.2.24 eliminates this vulnerability. Applying the patch 0f0a680d3df81739ea5088a2f88e65f938b7936b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 2026.2.0
- 2026.2.1
- 2026.2.2
- 2026.2.3
- 2026.2.4
- 2026.2.5
- 2026.2.6
- 2026.2.7
- 2026.2.8
- 2026.2.9
- 2026.2.10
- 2026.2.11
- 2026.2.12
- 2026.2.13
- 2026.2.14
- 2026.2.15
- 2026.2.16
- 2026.2.17
- 2026.2.18
- 2026.2.19
- 2026.2.20
- 2026.2.21
- 2026.2.22
- 2026.2.23
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CNA Base Score: 6.4
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Interpretation conflictCWE: CWE-436
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.2.24
Patch: 0f0a680d3df81739ea5088a2f88e65f938b7936b
Timeline
03/10/2026 CVE reserved03/21/2026 Advisory disclosed
03/21/2026 VulDB entry created
03/27/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-6rcp-vxwf-3mfp
Status: Confirmed
CVE: CVE-2026-32052 (🔒)
GCVE (CVE): GCVE-0-2026-32052
GCVE (VulDB): GCVE-100-352177
Entry
Created: 03/21/2026 06:58Updated: 03/27/2026 10:28
Changes: 03/21/2026 06:58 (78), 03/27/2026 10:28 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.