Affected: Homebrew: openclaw-cli

## Summary When multiple Google Chat webhook targets are registered on the same HTTP path, and request verification succeeds for more than one target, inbound webhook events could be routed by first-match semantics. This can cause cross-account policy/context misrouting.

## Affected Packages / Versions - npm: `openclaw` <= 2026.2.13 - npm: `clawdbot` <= 2026.1.24-3

## Details Affected component: `extensions/googlechat/src/monitor.ts`.

Baseline behavior allowed multiple webhook targets per path and selected the first target that passed `verifyGoogleChatRequest(...)`. In shared-path deployments where multiple targets can verify successfully (for example, equivalent audience validation), inbound events could be processed under the wrong account context (wrong allowlist/session/policy).

## Fix - Fix commit (merged to `main`): `61d59a802869177d9cef52204767cd83357ab79e` - `openclaw` will be patched in the next planned release: `2026.2.14`.

`clawdbot` is a legacy/deprecated package name; no patched version is currently planned. Migrate to `openclaw` and upgrade to `openclaw >= 2026.2.14`.

## Workaround Ensure each Google Chat webhook target uses a unique webhook path so routing is never ambiguous.

## Release Process Note The advisory is pre-populated with the planned patched version. After the npm release is published, the remaining action should be to publish the advisory.

Thanks @vincentkoc for reporting.

---

Fix commit 61d59a802869177d9cef52204767cd83357ab79e confirmed…

Affected: OpenClaw

OpenClaw versions prior to 2026.2.14 contain a webhook routing vulnerability in the Google Chat monitor component that allows cross-account policy context misrouting when multiple webhook targets share the same HTTP path. Attackers can exploit first-match request verification semantics to process inbound webhook events under incorrect account contexts, bypassing intended allowlists and session policies.