dbcve.org
OpenclawApplication

CVE-2026-32976

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 2026.3.11 or later.
See remediation →
71/100
Remediation priority · Elevated
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 authorization bypass vulnerability allowing channel commands to mutate protected sibling-account configuration despite configWrites restrictions. Attackers with authorized access on one account can execute channel commands like /config set channels.<provider>.accounts.<id> to modify configuration on target accounts with configWrites: false.

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 before 2026.3.11 contains an authorization bypass where channel commands can modify protected sibling-account configuration despite configWrites restrictions. Attackers with authorized access on one account can execute /config set commands on channels.<provider>.accounts.<id> to modify configuration on target accounts that should have configWrites: false.

MitigationUpdate to OpenClaw 2026.3.11 or later to patch the authorization bypass. Review and audit existing channel command permissions and account configurations for any unauthorized changes.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 application binary/package metadata to determine the exact version number
    Affected if Version is before 2026.3.11 (e.g., 2026.3.10, 2026.3.0, or any earlier release)
  2. Identify accounts with configWrites restrictions
    Examine the OpenClaw configuration files (typically in config/ or ~/.openclaw/) and search for accounts where configWrites is explicitly set to false
    Affected if Any account in the configuration has configWrites: false set, creating a protected sibling account
  3. Verify presence of sibling accounts
    Review the configuration for multiple accounts under the channels.<provider>.accounts section, noting any account IDs that differ from the one being used
    Affected if Multiple accounts exist under the same provider (e.g., channels.discord.accounts) where at least one has configWrites: false and others exist as siblings
  4. Test command access control (if safe to do in non-production)
    Using an account with channel command access, attempt to issue a /config set channels.<provider>.accounts.<sibling_id> command targeting a sibling account with configWrites: false
    Affected if The command executes successfully without authorization denial, indicating the bypass is present

Your environment is affected if you run OpenClaw version < 2026.3.11 AND have any account configured with configWrites: false alongside sibling accounts, as the authorization bypass allows modification of protected account configurations via channel commands.

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

Update to OpenClaw 2026.3.11 or later to patch the authorization bypass. Review and audit existing channel command permissions and account configurations for any unauthorized changes.

Recommended fix Moderate confidence

2026.3.11 or later

  1. Identify all OpenClaw instances running versions before 2026.3.11
  2. Take a backup of current configuration data
  3. Plan and schedule maintenance window for upgrade
  4. Upgrade OpenClaw to version 2026.3.11 or later
  5. Verify the upgrade was successful by checking the version number
  6. Test that accounts with configWrites: false can no longer be modified via channel commands from sibling accounts
  7. Confirm normal functionality of authorized configuration changes still works

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32976 — 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-32976 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