GHSA-CHM2-M3W2-WCXM

Google Chat allowlisting supports matching by sender email in addition to immutable sender resource name (users/<id>). This weakens identity binding if a deployment assumes allowlists are strictly keyed by immutable principals.

Affected Packages / Versions

(As of 2026-02-14; based on latest published npm versions)

• openclaw (npm): <= 2026.2.13
• clawdbot (npm): <= 2026.1.24-3

Details

Affected component:

• extensions/googlechat/src/monitor.ts

The allowFrom checks accept:

• Immutable sender id (users/<id>)
• Raw email ([email protected]) for usability

Historically, users/<email> was also treated as an email allowlist entry. This is now deprecated because it looks like an immutable ID but is actually a mutable principal.

Security Triage (2026-02-14)

Severity: Low

Rationale:

• Requests are authenticated as coming from Google Chat (token verification), so this is not a generic unauthenticated spoofing vector.
• A realistic exploit generally requires Google Workspace / IdP administrative control over identity lifecycle (e.g. reassigning an email address to a different underlying account) to obtain the same email with a different users/<id>.
• With that level of access, the attacker typically has broader compromise paths.

We still treat it as a valid defense-in-depth report because accepting mutable principals in authorization decisions can increase risk in chained-failure scenarios.

Remediation / Behavior Changes

Goal: preserve usability while reducing footguns.

• Raw email allowlists remain supported.
• users/<email> is deprecated and treated as a user id, not as an email allowlist.
• Documentation recommends users/<id> when strict immutable binding is required.

Fix Commit(s)

• c8424bf29a921e25663b29f308640b3d91a49432 (PR #16243)

Thanks @vincentkoc for reporting.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Kodem intelligence

1. What is GHSA-CHM2-M3W2-WCXM? GHSA-CHM2-M3W2-WCXM is a low-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.2.14. It is fixed in 2026.2.14. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. Which packages are affected by GHSA-CHM2-M3W2-WCXM?
   • openclaw (npm) (versions < 2026.2.14)
   • clawdbot (npm) (versions <= 2026.1.24-3)
3. Is there a fix for GHSA-CHM2-M3W2-WCXM? Yes. GHSA-CHM2-M3W2-WCXM is fixed in 2026.2.14. Upgrade to this version or later.
4. Is GHSA-CHM2-M3W2-WCXM exploitable, and should I be worried? Whether GHSA-CHM2-M3W2-WCXM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether GHSA-CHM2-M3W2-WCXM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix GHSA-CHM2-M3W2-WCXM? Upgrade openclaw to 2026.2.14 or later.