CVE-2026-28469: OpenClaw Google Chat webhook target ambiguity policy-context misrouting

CVE-2026-28469 · Severity: low · CVSS 3.1 · Published 2026-02-18

OpenClaw is a platform that routes incoming Google Chat webhooks to the correct account and applies the appropriate access policies. When multiple webhook targets are configured on the same HTTP path, the system may route incoming messages to the wrong account, causing that account's policies and session context to be applied incorrectly. An attacker could exploit this misconfiguration to access messages or trigger actions intended for a different account.

Technologies: clawdbot (npm), Openclaw. Vendors: npm, Openclaw.

Quick answers

Is CVE-2026-28469 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-28469 being exploited in the wild.
How severe is CVE-2026-28469?
Low severity, with a CVSS score of 3.1, published 18 February 2026.
Which products and versions are affected?
clawdbot (npm) SEMVER:introduced=0,last_affected=2026.1.24-3; Openclaw <= 2026.2.13.
Is there a fix for CVE-2026-28469?
A patch was published on 2026-02-18: Fixed in openclaw 2026.2.14 via commit 61d59a802869177d9cef52204767cd83357ab79e Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-28469 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-28469?
Check whether you run clawdbot (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This is an authorization bypass vulnerability in the Google Chat webhook routing logic (extensions/googlechat/src/monitor.ts). The vulnerable component accepts multiple webhook targets per HTTP path and selects the first target that passes request verification (verifyGoogleChatRequest). In deployments with shared paths where multiple targets have equivalent audience validation, inbound events are processed under the wrong account context, allowing an attacker to misroute webhook events to bypass access controls. The vulnerability requires a specific deployment configuration (multiple targets on same path with overlapping verification logic) but does not require authentication or user interaction. A patch is available in openclaw version 2026.2.14; clawdbot (a legacy package name) has no patch planned and users should migrate to openclaw.

Affected products

  • OpenClaw openclaw <= 2026.2.13
  • OpenClaw clawdbot <= 2026.1.24-3

Identifiers

  • CVE-2026-28469
  • GHSA-rq6g-px6m-c248

Timeline

  • 2026-02-18: disclosed
  • 2026-02-18: patched: Fixed in openclaw 2026.2.14 via commit 61d59a802869177d9cef52204767cd83357ab79e

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.