OpenClaw Webhook Routing Vulnerability in Google Chat Monitor Component Allows Cross-Account Policy Misrouting

A webhook routing vulnerability has been identified in OpenClaw versions prior to 2026.2.14, specifically within the Google Chat monitor component. This vulnerability allows cross-account policy context misrouting when multiple webhook targets share the same HTTP path. Exploitation of this vulnerability takes advantage of first-match request verification semantics, leading to the processing of inbound webhook events under incorrect account contexts and bypassing intended allowlists and session policies.

Impact

This vulnerability can cause cross-account policy/context misrouting, allowing webhook events to be processed under the wrong account, which can lead to unauthorized actions being taken based on incorrect policy contexts.

Reproduction

To reproduce this vulnerability, register multiple Google Chat webhook targets on the same HTTP path. Ensure that the verification process for each target can succeed. When an inbound webhook event is received, it may be routed to the first target that passed verification, regardless of the correct account context. This can be tested by sending a webhook event that triggers verification for multiple targets on the shared path.

Remediation

Users can upgrade to OpenClaw version 2026.2.14 or later to address this vulnerability. For those using the deprecated clawdbot package, it is recommended to migrate to OpenClaw and upgrade to version 2026.2.14 or later.