dbcve.org
OpenclawApplication

CVE-2026-32978

HIGH · 7.5 CVSS v3.1 Published 2026-03-29
Fix available
A fix is available. Upgrade to 2026.3.11 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
OpenClaw before 2026.3.11 contains an approval integrity vulnerability where system.run approvals fail to bind mutable file operands for certain script runners like tsx and jiti. Attackers can obtain approval for benign script commands, rewrite referenced scripts on disk, and execute modified code under the approved run context.

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 confidence

OpenClaw's system.run approval mechanism fails to bind mutable file operands for script runners like tsx and jiti. An attacker can obtain approval for a benign script, then rewrite the script file on disk before execution, causing the approved run context to execute attacker-modified code.

MitigationUpgrade to OpenClaw 2026.3.11 or implement file content hashing that binds approved scripts to their verified file state at execution time.

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
OpenclawApplication
Affected:< 2026.3.11

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed OpenClaw version
    Run 'openclaw --version' or check the package.json/package-lock.json for the installed openclaw version
    Affected if Version is less than 2026.3.11
  2. Identify system.run approval usage
    Search project configuration files for system.run approval rules, typically in openclaw.config.js, openclaw.config.ts, or similar configuration files in the project root
    Affected if system.run approval rules exist and tsx or jiti script runners are referenced in the approval configuration
  3. Verify script runner configuration
    Inspect the openclaw configuration for script runner definitions - look for 'tsx', 'jiti', or other script runner entries in the approval rules
    Affected if Script runners tsx or jiti are configured without file content binding
  4. Check for file content hashing implementation
    Review the approval logic code or configuration to determine if file content hashing (to bind approved scripts to their verified file state at execution time) is implemented
    Affected if No file content hashing mechanism is present in the approval workflow

A user is affected if OpenClaw version is below 2026.3.11 AND system.run approval is configured with tsx or jiti script runners without file content hash verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.3.11 or later
Fixed in 2026.3.11
Interim mitigation

Upgrade to OpenClaw 2026.3.11 or implement file content hashing that binds approved scripts to their verified file state at execution time.

Recommended fix Moderate confidence

2026.3.11

  1. 1. Backup your current Openclaw installation and configuration
  2. 2. Identify your current Openclaw version by checking the application or configuration files
  3. 3. Download Openclaw version 2026.3.11 or later from the official GitHub repository
  4. 4. Stop the Openclaw service or application
  5. 5. Replace the existing Openclaw installation files with the new version
  6. 6. Verify the integrity of the downloaded package using checksums if available
  7. 7. Restart the Openclaw service
  8. 8. Verify that the approval integrity vulnerability is resolved by testing that system.run approvals now properly bind mutable file operands
Caveat Review release notes for any configuration or API changes between your current version and 2026.3.11

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32978 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32978 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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