Skip to main content
VulnerabilityPublished Updated

CVE-2026-32974: OpenClaw · Feishu webhook mode accepted forged events when only `verificationToken` was configured

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 2026.3.12 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.12.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.3.12
Fixed in
  • 2026.3.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied by upgrading OpenClaw CLI to version 2026.3.12 or later. The fix enforces that Feishu webhook mode fails closed unless an encryptKey is configured and rejects missing or invalid signatures before processing events. Deployments must configure the encryptKey parameter for webhook security. No additional mitigation is required once updated and properly configured.

Description

OpenClaw CLI versions before 2026.3.12 allowed Feishu webhook mode deployments configured only with a verificationToken but without an encryptKey. This weaker configuration permitted acceptance of forged inbound events due to insufficient cryptographic verification. An unauthenticated attacker with network access to the webhook endpoint could inject forged Feishu events, impersonate senders, and potentially trigger downstream tool execution based on local agent policies. The vulnerability is fixed in version 2026.3.12, which enforces the presence of encryptKey and rejects missing or invalid signatures.

References

Community reviews

Loading reviews…