dbcve.org
OpenclawApplication

CVE-2026-32975

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-29
Fix available
A fix is available. Upgrade to 2026.3.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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.12 contains a weak authorization vulnerability in Zalouser allowlist mode that matches mutable group display names instead of stable group identifiers. Attackers can create groups with identical names to allowlisted groups to bypass channel authorization and route messages from unintended groups to the agent.

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.12 has a weak authorization vulnerability in Zalouser allowlist mode where group authorization checks match against mutable group display names rather than stable group identifiers. Attackers can create new groups with display names identical to allowlisted groups to bypass channel authorization and route messages from unauthorized groups to the agent.

MitigationUpgrade to OpenClaw version 2026.3.12 or later, which should implement stable group identifier-based allowlist matching instead of relying on display names.

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.12

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
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 checks

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

  1. Determine OpenClaw installation and version
    Run 'openclaw --version' or check the installed package version via your package manager (pip, npm, etc.)
    Affected if The installed version is any version before 2026.3.12
  2. Identify if Zalouser allowlist mode is enabled
    Inspect the OpenClaw configuration file (typically openclaw.yaml, openclaw.json, or similar in the config directory) for a setting like 'zalouser.allowlist_mode', 'zalouser.mode', or 'authorization.mode' set to 'allowlist' or 'whitelist'
    Affected if Zalouser allowlist mode is explicitly enabled in the configuration
  3. List configured allowlisted groups
    Search the configuration file for entries under sections like 'zalouser.allowed_groups', 'allowlist', 'whitelist', or 'authorized_groups' to identify which group display names are permitted
    Affected if One or more groups are explicitly allowlisted by display name in the configuration
  4. Check for duplicate or conflicting group display names
    Query the group directory or audit log for groups whose display names match any entry in the allowlist, noting any newly created groups with identical names
    Affected if Multiple groups exist with the same display name as an allowlisted entry, or recently created groups match allowlisted names
  5. Verify authorization uses stable group identifiers
    Review the source code or configuration to determine if group authorization logic compares against stable group IDs (UUIDs, internal IDs) or against mutable display names
    Affected if The authorization logic compares against display names rather than stable identifiers

You are affected if OpenClaw version is before 2026.3.12 AND Zalouser allowlist mode is enabled AND your authorization logic matches against display names instead of stable group identifiers.

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.12 or later
Fixed in 2026.3.12
Interim mitigation

Upgrade to OpenClaw version 2026.3.12 or later, which should implement stable group identifier-based allowlist matching instead of relying on display names.

Recommended fix Moderate confidence

2026.3.12

  1. 1. Identify the current installed version of OpenClaw
  2. 2. Plan maintenance window for the upgrade
  3. 3. Backup current OpenClaw configuration and data
  4. 4. Upgrade OpenClaw to version 2026.3.12 or later
  5. 5. Verify the upgrade was successful and the application is functioning
  6. 6. Test that the authorization mechanism now uses stable group identifiers instead of display names

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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