openclaw
Affected
- introduced
0, fixed2026.2.14(semver)
Fixed versions
2026.2.14
Fix
- Fixed version
2026.2.14npm install [email protected]
Advisory
Also known as: CVE-2026-28469
OpenClaw Google Chat shared-path webhook target ambiguity allowed cross-account policy-context misrouting
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
openclaw <= 2026.2.13clawdbot <= 2026.1.24-3Details
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
main): 61d59a802869177d9cef52204767cd83357ab79eopenclaw 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.
High Basis: The source's own band: HIGH
0, fixed 2026.2.14 (semver)2026.2.14
2026.2.14npm install [email protected]0, last affected 2026.1.24-3 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0