Executive brief
OpenClaw is a platform that routes incoming Google Chat webhooks to the correct account and applies the appropriate access policies. When multiple webhook targets are configured on the same HTTP path, the system may route incoming messages to the wrong account, causing that account's policies and session context to be applied incorrectly. An attacker could exploit this misconfiguration to access messages or trigger actions intended for a different account.
Technical details
This is an authorization bypass vulnerability in the Google Chat webhook routing logic (extensions/googlechat/src/monitor.ts). The vulnerable component accepts multiple webhook targets per HTTP path and selects the first target that passes request verification (verifyGoogleChatRequest). In deployments with shared paths where multiple targets have equivalent audience validation, inbound events are processed under the wrong account context, allowing an attacker to misroute webhook events to bypass access controls. The vulnerability requires a specific deployment configuration (multiple targets on same path with overlapping verification logic) but does not require authentication or user interaction. A patch is available in openclaw version 2026.2.14; clawdbot (a legacy package name) has no patch planned and users should migrate to openclaw.
Affected products
- OpenClaw openclaw <= 2026.2.13
- OpenClaw clawdbot <= 2026.1.24-3
Timeline
- 2026-02-18: disclosed
- 2026-02-18: patched: Fixed in openclaw 2026.2.14 via commit 61d59a802869177d9cef52204767cd83357ab79e