How severe is GHSA-chm2-m3w2-wcxm?

No CVSS score has been assigned to GHSA-chm2-m3w2-wcxm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-chm2-m3w2-wcxm?

GHSA-chm2-m3w2-wcxm affects the following packages: openclaw (npm), clawdbot (npm). Ecosystems affected: npm.

How do I fix GHSA-chm2-m3w2-wcxm?

Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chm2-m3w2-wcxm is resolved across your whole dependency graph.

How do I detect GHSA-chm2-m3w2-wcxm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-chm2-m3w2-wcxm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-chm2-m3w2-wcxm?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-chm2-m3w2-wcxm can be triaged on real exposure rather than presence alone.

Is GHSA-chm2-m3w2-wcxm actively exploited in the wild?

No public exploit code has been indexed for GHSA-chm2-m3w2-wcxm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-chm2-m3w2-wcxm published, and has it been updated?

GHSA-chm2-m3w2-wcxm was published on February 17, 2026 and was last updated on February 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-chm2-m3w2-wcxm — openclaw

Fix: openclaw/openclaw#16243

GHSA-chm2-m3w2-wcxm is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw Google Chat spoofing access with allowlist authorized mutable email principal despite sender-ID mismatch

Published

Feb 17, 2026

Updated

Feb 17, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Feb 17, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

3.0Mdownloads / week

clawdbotnpm

942downloads / week

Description

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 ([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.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.14`npm install openclaw@2026.2.14`
📦npm	`clawdbot`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chm2-m3w2-wcxm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-chm2-m3w2-wcxm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-chm2-m3w2-wcxm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 (`[email protected]`) for usability H

O3 Security · Impact-Aware SCA

Is GHSA-chm2-m3w2-wcxm in your dependencies?

O3 Security finds GHSA-chm2-m3w2-wcxm across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works