OpenClaw Google Chat monitor is vulnerable to a critical policy bypass that allows attackers to misroute webhook events and bypass session security controls.

The Google Chat monitor component contains a webhook routing flaw where multiple targets sharing the same HTTP path lead to context misrouting. An unauthenticated attacker can exploit "first-match" verification logic to force the system to process events under an incorrect account context, effectively bypassing session policies and allowlists.

This vulnerability compromises the multi-tenancy and access control integrity of the OpenClaw platform. An attacker could gain unauthorized access to data or trigger actions within another user's account context, leading to data leaks and unauthorized configuration changes. The CVSS score of 9.8 highlights the severity of this architectural failure in enforcing account isolation.

Immediate Action: Update the OpenClaw Google Chat monitor to version 2026.2.14 or later to resolve the webhook routing logic error.

Proactive Monitoring: Audit webhook delivery logs for requests that appear to be processed under mismatched account IDs or originate from unexpected sources.

Compensating Controls: Use unique, non-predictable HTTP paths for each webhook target to prevent path collisions and minimize the risk of misrouting.

Public Exploit Available: No

The ability to bypass account-level security policies through routing manipulation is a critical security failure. Security teams must ensure that OpenClaw instances are updated to the patched version immediately. Furthermore, verify that all webhook configurations utilize unique identifiers to ensure robust isolation between different account contexts.