Openclaw cli: OpenClaw Google Chat shared-path webhook target ambiguity allowed cross-account policy-context
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2026.2.14 as a priority.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.14
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in openclaw version 2026.2.14. Users should upgrade to openclaw >=2026.2.14 to remediate this vulnerability. For users of the deprecated clawdbot package, migration to openclaw and upgrading to the patched version is advised. As a workaround before patching, ensure that each Google Chat webhook target uses a unique webhook path to prevent ambiguous routing.
Description
OpenClaw CLI versions prior to 2026.2.14 have a vulnerability in Google Chat webhook handling where multiple webhook targets registered on the same HTTP path can cause cross-account policy misrouting. This occurs because the system routes inbound webhook events to the first matching target that verifies the request, potentially processing events under the wrong account context. The issue is fixed in OpenClaw version 2026.2.14. Users of the deprecated clawdbot package should migrate to OpenClaw and upgrade accordingly. A workaround is to ensure each webhook target uses a unique path to avoid ambiguous routing.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-rq6g-px6m-c248 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-28469 (opens in a new tab)
- github.com/openclaw/openclaw/commit/61d59a802869177d9cef52204767cd83357ab79e (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- github.com/openclaw/openclaw/releases/tag/v2026.2.14 (opens in a new tab)
- vulncheck.com/advisories/openclaw-cross-account-policy-context-misrouting-via-shared-webhook-path-ambiguity (opens in a new tab)