CVE-2026-32052
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenClaw 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenClaw versions before 2026.2.24 have a command injection vulnerability in the system.run shell-wrapper where attackers can inject hidden commands by appending trailing positional arguments after inline shell payloads. These trailing argv carriers bypass display context validation, allowing arbitrary command execution while displaying misleading approval text to users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.2.24CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check OpenClaw installed versionRun 'openclaw --version' or check the package metadata file (e.g., pyproject.toml, setup.py, or version file in the installation directory) to determine the exact version numberAffected if The installed version is lower than 2026.2.24
-
Locate the system.run function configurationSearch for configuration files or code that defines or enables the system.run function. Look in config files, plugin directories, or the main application configuration for entries named 'system.run', 'shell-wrapper', or similarAffected if The system.run function is defined, enabled, or loaded in the OpenClaw configuration
-
Verify if system.run accepts user-supplied argumentsInspect the source code or configuration of the system.run function to determine if it processes trailing positional arguments (argv) as part of its execution flowAffected if The system.run function processes or passes through trailing positional arguments to the underlying shell command
-
Check for shell metacharacters in recent system.run invocationsReview application logs, audit logs, or command history files for entries involving system.run that contain shell metacharacters (such as ;, |, &, $, `, or >) in what appear to be argument positionsAffected if Logs show system.run calls with suspicious shell metacharacters in argument positions indicating potential exploitation attempts
You are affected if OpenClaw version is below 2026.2.24 AND the system.run shell-wrapper function is enabled and configured to accept trailing positional arguments that could be exploited for command injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.2.24
Upgrade to OpenClaw version 2026.2.24 or later. Additionally, implement strict input validation on the system.run shell-wrapper to sanitize and reject any unexpected positional arguments.
2026.2.24
- Identify the current Openclaw installation version
- Download or fetch Openclaw version 2026.2.24 or later from the official repository
- Review the patch commit (0f0a680d3df81739ea5088a2f88e65f938b7936b) to understand the code changes
- Stop the Openclaw service before upgrading
- Replace the existing installation with the new version 2026.2.24
- Verify the system.run shell-wrapper code now properly validates and sanitizes all positional arguments
- Restart the Openclaw service
- Confirm the fix by testing that command injection via trailing positional arguments is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32052 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32052 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data