CVE-2026-32971
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 before 2026.3.11 contains an approval-integrity vulnerability in node-host system.run approvals that displays extracted shell payloads instead of the executed argv. Attackers can place wrapper binaries and induce wrapper-shaped commands to execute local code after operators approve misleading command text.
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 · high confidenceOpenClaw before 2026.3.11 has an approval-integrity flaw in its node-host system.run approvals where the command displayed to operators for approval differs from what actually executes - the system shows the argv but extracts and executes shell payloads instead. Attackers can place wrapper binaries that appear benign when approved but execute malicious local code.
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.3.11CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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.
-
Identify OpenClaw installation and versionLocate the OpenClaw installation directory and determine the installed version by inspecting version metadata files, executable properties, or running version inquiry commandsAffected if The installed version is lower than 2026.3.11
-
Verify node-host system.run approval mechanism is in useInspect OpenClaw configuration files or runtime settings to determine whether the node-host system.run command approval feature is enabled or configuredAffected if The system.run approval mechanism is enabled and active in the environment
-
Inspect approval dialog command display behaviorTrigger a system.run approval prompt and observe whether the displayed command matches the literal argv arguments or appears as a shell-expanded or extracted payloadAffected if Approval dialogs display modified or extracted shell payloads rather than the original command arguments
-
Audit for wrapper binaries in command execution pathsExamine the system PATH and OpenClaw's configured execution directories for any wrapper or proxy binaries that could intercept approvals and substitute different commandsAffected if Wrapper binaries exist that could present benign text in approvals while executing different commands after user consent
A system is affected if OpenClaw version is below 2026.3.11, the node-host system.run approval feature is enabled, and approval dialogs display shell-expanded payloads instead of literal argv arguments, potentially allowing wrapper binaries to bypass user consent.
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.3.11
Update to OpenClaw 2026.3.11 or later which fixes the approval integrity issue; operators should verify command integrity through additional validation before approving.
2026.3.11
- Upgrade OpenClaw to version 2026.3.11 or later to resolve the approval-integrity vulnerability where shell payloads are displayed instead of executed argv in system.run approvals
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32971 — 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-32971 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