Is this vulnerability remotely exploitable?

Yes. If the webhook endpoint is exposed to the internet or to external Google Chat integrations, an attacker who can send HTTP requests to the shared path can potentially trigger cross-account context misrouting.

What level of access does an attacker need to exploit this issue?

The attacker typically needs the ability to post to the vulnerable webhook URL, either by controlling a Google Chat space/bot configured with that URL or by directly reaching the endpoint over HTTP. No additional privileges on the OpenClaw platform are required beyond that network or integration access.

What is the safest general fix pattern for this kind of flaw?

The most robust fix is to enforce a one-to-one binding between webhook identifiers and accounts—using unique URLs or strong per-account secrets—and to perform authorization based on those unique identifiers before establishing any account context. Shared paths without a disambiguating secret or ID should be eliminated.

Severity:

HIGH RISK

(7.5)

Improper Authorization by Account Context (CWE-639) in OpenClaw Google Chat Webhook Routing

CVE-2026-28469

Published:

Mar 5, 2026

Status:

Received

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Improper Authorization / Context Confusion

CWE:

CWE-639

Impact:

Cross-Account Policy Bypass and Unauthorized Action Execution

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Authorization / Context Confusion

CWE:

CWE-639

Impact:

Cross-Account Policy Bypass and Unauthorized Action Execution

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Improper Authorization by Account Context (CWE-639) in OpenClaw Google Chat Webhook Routing

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare