CVE-2026-28469
Cross-Account Webhook Misrouting in OpenClaw Google Chat Monitor
Publication date: 2026-03-05
Last updated on: 2026-03-09
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.14 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized processing of webhook events under incorrect account contexts. This means attackers could bypass security controls such as allowlists and session policies, potentially leading to unauthorized access or actions within affected systems.
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions prior to 2026.2.14 within the Google Chat monitor component. It is a webhook routing vulnerability that occurs when multiple webhook targets share the same HTTP path. Due to the way requests are verified using a first-match approach, inbound webhook events can be processed under incorrect account contexts. This misrouting allows attackers to bypass intended allowlists and session policies.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know