Lucene search
+L

45 matches found

CVE
CVE
added 2026/03/29 12:44 p.m.33 views

CVE-2026-32974

OpenClaw suffers an authentication bypass in Feishu webhook mode when only verificationToken is configured without encryptKey, allowing unauthenticated attackers to inject forged Feishu events and trigger downstream tool execution via the webhook endpoint. Affected software: OpenClaw prior to ver...

9.8CVSS6.1AI score0.00247EPSS
SaveExploits0References2Affected Software1
OSV
OSV
added 2026/03/29 12:44 p.m.5 views

CVE-2026-32974 OpenClaw < 2026.3.12 - Forged Event Injection via Feishu Webhook Verification Token

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

8.8CVSS6.1AI score0.00247EPSS
SaveExploits0References4
Positive Technologies
Positive Technologies
added 2026/03/29 12:0 a.m.4 views

PT-2026-28455

Name of the Vulnerable Software and Affected Versions OpenClaw versions prior to 2026.3.12 Description OpenClaw is susceptible to an authentication bypass issue in Feishu webhook mode. This occurs when only the verificationToken is configured, and the encryptKey is not. This allows unauthenticate...

8.8CVSS6.1AI score0.00247EPSS
SaveExploits0References6
OSV
OSV
added 2026/03/13 8:55 p.m.5 views

GHSA-G353-MGV3-8PCJ OpenClaw: Feishu webhook mode accepted forged events when only `verificationToken` was configured

Summary Feishu webhook mode allowed deployments that configured only verificationToken without encryptKey. In that state, forged inbound events could be accepted because the weaker configuration did not provide the required cryptographic verification boundary. Impact An unauthenticated network...

8.6CVSS6.1AI score0.00247EPSS
SaveExploits0References7
Github Security Blog
Github Security Blog
added 2026/03/13 8:55 p.m.24 views

OpenClaw: Feishu webhook mode accepted forged events when only `verificationToken` was configured

Summary Feishu webhook mode allowed deployments that configured only verificationToken without encryptKey. In that state, forged inbound events could be accepted because the weaker configuration did not provide the required cryptographic verification boundary. Impact An unauthenticated network...

9.8CVSS5.9AI score0.00247EPSS
SaveExploits0References7Affected Software1
Rows per page
Query Builder