NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · OpenClaw

CVE-2026-28469: OpenClaw Google Chat shared-path webhook target ambiguity allowed cross-account policy-context misrouting

highCVSS 4.0 8.3 · 3.1 9.8GHSA-rq6g-px6m-c248

OpenClaw's Google Chat extension let several webhook targets share one HTTP path and picked the first one whose request verification passed. When more than one target verified, events ran under the wrong account's allowlist, session and policy. `openclaw` below 2026.2.14 is affected. Upgrade to 2026.2.14. The legacy `clawdbot` package has no patch.

Published Feb 18, 2026 · Updated Mar 6, 2026 · Analysis Oct 31, 2026

What an attacker can do

In extensions/googlechat/src/monitor.ts, the handler looped over the targets registered for a path and chose the first that passed verifyGoogleChatRequest(...). If two accounts share a path and both verify, for example because their audience validation is equivalent, the choice depends only on order (CWE-284, CWE-639).

The event is then processed under the wrong account context: the wrong allowlist, session and policy. A sender who is allowed in one account's context may be treated by another account's rules, and messages can land in a session they should not reach. The attacker does not need credentials in the CVSS 3.1 vector, which scores 9.8, while the 4.0 vector marks the attack as high complexity with present preconditions, 8.3. The precondition is a shared-path, multi-target deployment, which is uncommon.

For teams that run several Google Chat accounts or bots through one OpenClaw instance, the result is cross-account policy bypass: another tenant's agent, tools and permissions answer the message. Single-account setups are not affected.

Who is affected

The npm package openclaw at 2026.2.13 or earlier, and the legacy npm package clawdbot at 2026.1.24-3 or earlier. You are exposed only if more than one Google Chat webhook target is registered on the same path. Check:

npm ls -g openclaw clawdbot

Then review the Google Chat channel config for accounts that use the same webhook path.

openclaw

Ecosystem
npm
Affected
< 2026.2.14
Fixed in
2026.2.14
Check
npm ls openclaw

clawdbot

Ecosystem
npm
Affected
<= 2026.1.24-3
Fixed in
No patched version yet
Check
npm ls clawdbot

How to fix it

Upgrade to openclaw 2026.2.14, the patched version (commit 61d59a8):

npm install -g [email protected]

The handler now collects all matching targets. With more than one match it returns 401 "ambiguous webhook target" and processes nothing. clawdbot is a legacy, deprecated package name with no patched version planned, so migrate to openclaw. Workaround from the advisory: give each Google Chat webhook target a unique webhook path so routing is never ambiguous.

How to tell if you were hit

Review the Google Chat configuration for two or more accounts sharing one webhook path. In logs, look for events handled under an account that did not own the conversation. After upgrading, a 401 response with "ambiguous webhook target" means a shared path is still configured and needs unique paths.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

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 on main and in v2026.2.14. Upgrade to openclaw >= 2026.2.14.

Credited to vincentkoc.

Questions

Am I affected if I run a single Google Chat account?

The advisory describes shared-path deployments with several targets. With one target per path there is no ambiguity to resolve.

Is the clawdbot package patched?

No. It is a legacy name, affected up to 2026.1.24-3, and no patch is planned. Migrate to openclaw 2026.2.14 or later.

What is the quickest mitigation?

Give every Google Chat webhook target its own unique path, so routing never depends on first-match order.

What happens after the fix?

If more than one target verifies on a path, the request is rejected with 401 "ambiguous webhook target" and the event is not processed.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries