GHSA-chm2-m3w2-wcxm: Openclaw OpenClaw Google Chat Spoofing Access Vulnerability

LOW
CWE-863 CWE-290
Published
Advisory Summary

GHSA-chm2-m3w2-wcxm is a LOW openclaw google chat spoofing access vulnerability (CWE-863: Incorrect Authorization) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw google chat spoofing access with allowlist authorized mutable email principal despite sender-id mismatch. Remediation is available by upgrading affected packages to version 2026.2.14.

GHSA-chm2-m3w2-wcxm at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-chm2-m3w2-wcxm
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product Openclaw
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-chm2-m3w2-wcxm

To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.2.14
npm install openclaw@2026.2.14
clawdbot fixed: Latest secure release
npm install clawdbot@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-chm2-m3w2-wcxm, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.14), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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 (`alice@example.com`) 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.

GHSA-chm2-m3w2-wcxm Affected Openclaw Versions

2 component(s)
Fixed Versions:
2026.2.14
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm
< 2026.2.14
2026.2.14
clawdbot
npm
≤ 2026.1.24-3

References

Frequently Asked Questions

What is GHSA-chm2-m3w2-wcxm?
GHSA-chm2-m3w2-wcxm is a security vulnerability in Openclaw involving OpenClaw Google Chat spoofing access with allowlist authorized mutable email principal despite sender-ID mismatch under CWE-863: Incorrect Authorization.
Which Openclaw versions are affected?
Affected versions include releases prior to 2026.2.14 across affected packages: openclaw, clawdbot.
What version fixes GHSA-chm2-m3w2-wcxm?
Upgrading to 2026.2.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.2.14. Upgrade your dependency to 2026.2.14 or later.
Is clawdbot affected?
Yes, clawdbot is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-chm2-m3w2-wcxm?
GHSA-chm2-m3w2-wcxm is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check npm dependencies for GHSA-chm2-m3w2-wcxm?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-chm2-m3w2-wcxm",
  "modified" : "2026-02-17T22:56:39Z",
  "published" : "2026-02-17T22:56:39Z",
  "aliases" : [ ],
  "summary" : "OpenClaw Google Chat spoofing access with allowlist authorized mutable email principal despite sender-ID mismatch",
  "details" : "### Summary\nGoogle 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.\n\n### Affected Packages / Versions\n(As of 2026-02-14; based on latest published npm versions)\n- `openclaw` (npm): `<= 2026.2.13`\n- `clawdbot` (npm): `<= 2026.1.24-3`\n\n### Details\nAffected component:\n- `extensions/googlechat/src/monitor.ts`\n\nThe `allowFrom` checks accept:\n- Immutable sender id (`users/<id>`)\n- Raw email (`alice@example.com`) for usability\n\nHistorically, `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.\n\n### Security Triage (2026-02-14)\nSeverity: **Low**\n\nRationale:\n- Requests are authenticated as coming from Google Chat (token verification), so this is not a generic unauthenticated spoofing vector.\n- 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>`.\n- With that level of access, the attacker typically has broader compromise paths.\n\nWe still treat it as a valid defense-in-depth report because accepting mutable principals in authorization decisions can increase risk in chained-failure scenarios.\n\n### Remediation / Behavior Changes\nGoal: preserve usability while reducing footguns.\n- Raw email allowlists remain supported.\n- `users/<email>` is deprecated and treated as a **user id**, not as an email allowlist.\n- Documentation recommends `users/<id>` when strict immutable binding is required.\n\n### Fix Commit(s)\n- `c8424bf29a921e25663b29f308640b3d91a49432` (PR #16243)\n\nThanks @vincentkoc for reporting.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.14"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "clawdbot"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "2026.1.24-3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-chm2-m3w2-wcxm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/pull/16243"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/c8424bf29a921e25663b29f308640b3d91a49432"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/releases/tag/v2026.2.14"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-290", "CWE-863" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-17T22:56:39Z",
    "nvd_published_at" : null
  }
}