dbcve.org
OpenclawApplication

CVE-2026-32924

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 an authorization bypass vulnerability where Feishu reaction events with omitted chat_type are misclassified as p2p conversations instead of group chats. Attackers can exploit this misclassification to bypass groupAllowFrom and requireMention protections in group chat reaction-derived events.

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 confidence

OpenClaw before 2026.3.12 has an authorization bypass where Feishu reaction events with omitted chat_type are incorrectly classified as p2p conversations rather than group chats. This misclassification allows attackers to circumvent groupAllowFrom and requireMention protections that should apply to group chat reaction events.

MitigationUpgrade to OpenClaw version 2026.3.12 or later which properly validates chat_type before classifying conversation types.

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. Identify OpenClaw installation version
    Run the command to display the installed OpenClaw version (e.g., openclaw --version, check package.json, or inspect the binary metadata)
    Affected if The installed version is earlier than 2026.3.12
  2. Confirm Feishu integration is enabled
    Check the OpenClaw configuration for Feishu/Lark bot integration settings - look for Feishu app credentials, webhook configurations, or bot enablement flags
    Affected if Feishu integration is configured and active in the environment
  3. Verify reaction event handling configuration
    Inspect the Feishu event subscription configuration to confirm reaction events (reaction_added) are subscribed and processing is enabled
    Affected if Reaction event processing from Feishu is enabled and chat_type field handling is not explicitly validated
  4. Check groupAllowFrom protection status
    Review the OpenClaw access control or security policy configuration for groupAllowFrom rules that should apply to group chat reaction events
    Affected if groupAllowFrom protections exist but may be bypassed due to chat_type misclassification
  5. Check requireMention protection status
    Review the OpenClaw security configuration for requireMention rules that should enforce mention requirements on group chat reactions
    Affected if requireMention protections exist but may be bypassed due to chat_type misclassification

Environment is affected if OpenClaw version is earlier than 2026.3.12 AND Feishu integration with reaction events is enabled AND groupAllowFrom or requireMention protections are configured for group chats.

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 properly validates chat_type before classifying conversation types.

Recommended fix Moderate confidence

Openclaw 2026.3.12

  1. 1. Back up your current Openclaw installation and configuration files.
  2. 2. Review the release notes for version 2026.3.12 to understand any changes in behavior related to chat type classification.
  3. 3. Download the updated Openclaw package version 2026.3.12 from the official repository.
  4. 4. Stop the Openclaw service before applying the update.
  5. 5. Install the version 2026.3.12 package, preserving your existing configuration.
  6. 6. Start the Openclaw service and verify it is running correctly.
  7. 7. Test Feishu reaction events in both p2p and group chat scenarios to confirm the chat_type is now correctly classified.
  8. 8. Verify that groupAllowFrom and requireMention protections are functioning as expected for group chat reaction-derived events.
Caveat Security fix may alter behavior for reaction events with omitted chat_type; test thoroughly in non-production environment first

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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