CVE-2026-32920
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.12 automatically discovers and loads plugins from .OpenClaw/extensions/ without explicit trust verification, allowing arbitrary code execution. Attackers can execute malicious code by including crafted workspace plugins in cloned repositories that execute when users run OpenClaw from the directory.
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 versions before 2026.3.12 automatically discover and load plugins from the .OpenClaw/extensions/ directory without performing any trust verification or signature validation. This allows attackers to place malicious plugins in cloned repositories that execute arbitrary code when users run OpenClaw from that directory.
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.12CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check OpenClaw versionRun 'openclaw --version' or check the application manifest/binary metadata to determine the installed version numberAffected if The installed version is before 2026.3.12 (or 6.3.12)
-
Locate the extensions directoryCheck for the existence of .OpenClaw/extensions/ directory in the current working directory or in the user's home directoryAffected if The .OpenClaw/extensions/ directory exists and contains plugin files
-
Inspect plugin contentsList all files in the .OpenClaw/extensions/ directory and examine any .py, .so, or binary plugin files for suspicious code or unexpected originsAffected if Any plugins are present from untrusted or unknown sources
-
Identify working directory at runtimeDetermine the directory from which OpenClaw is being executed; check if it is a cloned repository or shared directoryAffected if OpenClaw is run from a directory containing untrusted repositories that could contain malicious plugins
You are affected if your OpenClaw version is earlier than 2026.3.12 and the .OpenClaw/extensions/ directory contains plugins, especially if running from a cloned or shared repository directory.
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.12
Upgrade to OpenClaw 2026.3.12 or later which implements plugin trust validation. Until then, avoid running OpenClaw in untrusted directories and delete any .OpenClaw/extensions/ folders from cloned repositories before use.
OpenClaw 2026.3.12
- Upgrade OpenClaw to version 2026.3.12 or later to resolve the arbitrary code execution vulnerability
- After upgrading, verify that plugin loading from .OpenClaw/extensions/ now requires explicit trust verification
- Confirm the upgrade was successful by checking the OpenClaw version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32920 — 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-32920 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