dbcve.org
OpenclawApplication

CVE-2026-32974

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 authentication bypass vulnerability in Feishu webhook mode when only verificationToken is configured without encryptKey, allowing acceptance of forged events. Unauthenticated network attackers can inject forged Feishu events and trigger downstream tool execution by reaching the webhook endpoint.

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 version 2026.3.12 has an authentication bypass in its Feishu webhook integration. When only verificationToken is configured without encryptKey, the system fails to properly validate incoming Feishu events, allowing unauthenticated attackers to inject forged events that trigger downstream tool execution via the webhook endpoint.

MitigationUpgrade to OpenClaw 2026.3.12 or later and ensure both verificationToken AND encryptKey are properly configured for the Feishu webhook integration to enable proper event validation.

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. Check OpenClaw installed version
    Retrieve the installed version of OpenClaw using the system's package manager or application version command, then compare it to the affected range: versions prior to 2026.3.12
    Affected if The installed version is before 2026.3.12
  2. Verify Feishu webhook integration is configured
    Locate and inspect the OpenClaw configuration files or settings where webhook integrations are defined; look for Feishu-specific configuration entries
    Affected if Feishu webhook integration is enabled or configured in the system
  3. Confirm verificationToken is present
    Within the Feishu webhook configuration, check for the presence of a verificationToken setting and note its value
    Affected if A verificationToken is configured for the Feishu webhook
  4. Verify encryptKey is absent
    Within the Feishu webhook configuration, check whether an encryptKey or encryption key is defined; if this field is missing or empty, the vulnerability condition exists
    Affected if No encryptKey is configured or the encryptKey field is empty or absent
  5. Assess webhook endpoint network exposure
    Determine if the Feishu webhook endpoint (typically the URL endpoint handling Feishu events) is accessible from untrusted networks or the public internet
    Affected if The webhook endpoint is externally accessible without additional network restrictions

You are affected if OpenClaw version is below 2026.3.12 AND the Feishu webhook has verificationToken configured but lacks encryptKey, allowing unauthenticated event injection.

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 2026.3.12 or later and ensure both verificationToken AND encryptKey are properly configured for the Feishu webhook integration to enable proper event validation.

Recommended fix High confidence

OpenClaw 2026.3.12

  1. Upgrade OpenClaw to version 2026.3.12 or later
  2. After upgrading, verify that Feishu webhook mode is configured with BOTH verificationToken AND encryptKey (not just verificationToken alone)
  3. Test the webhook endpoint to confirm it properly validates signatures using the encryptKey

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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