How severe is GHSA-chfm-xgc4-47rj?

No CVSS score has been assigned to GHSA-chfm-xgc4-47rj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-chfm-xgc4-47rj?

GHSA-chfm-xgc4-47rj affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-chfm-xgc4-47rj?

Update openclaw to 2026.3.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chfm-xgc4-47rj is resolved across your whole dependency graph.

How do I detect GHSA-chfm-xgc4-47rj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-chfm-xgc4-47rj 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-chfm-xgc4-47rj?

O3 pinpoints whether GHSA-chfm-xgc4-47rj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-chfm-xgc4-47rj actively exploited in the wild?

No public exploit code has been indexed for GHSA-chfm-xgc4-47rj 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.

What type of vulnerability is GHSA-chfm-xgc4-47rj?

GHSA-chfm-xgc4-47rj is classified as CWE-441 (CWE-441). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-chfm-xgc4-47rj published, and has it been updated?

GHSA-chfm-xgc4-47rj was published on April 2, 2026 and was last updated on May 8, 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

GHSA-chfm-xgc4-47rj

Fix: openclaw/openclaw@5cca380

GHSA-chfm-xgc4-47rj is a CWE-441 vulnerability in openclaw. O3 Security confirms whether GHSA-chfm-xgc4-47rj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: MSTeams thread history bypasses sender allowlist via Graph API

Also known asCVE-2026-41365

Published

Apr 2, 2026

Updated

May 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.2Mdownloads / week

Description

Summary

MSTeams thread history bypasses sender allowlist via Graph API

Current Maintainer Triage

Status: open
Normalized severity: medium
Assessment: Real in shipped v2026.3.28 MS Teams because Graph-fetched thread history bypasses sender allowlists, with unreleased mainline filtering fix.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version: 2026.3.31
Vulnerable version range: <=2026.3.28
Patched versions: >= 2026.3.31
First stable tag containing the fix: v2026.3.31

Fix Commit(s)

5cca38084074fb5095aa11b6a59820d63e4937c9 — 2026-03-30T15:38:26+01:00

OpenClaw thanks @AntAISecurityLab for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.31

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.3.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chfm-xgc4-47rj 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 pinpoints whether GHSA-chfm-xgc4-47rj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-chfm-xgc4-47rj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary MSTeams thread history bypasses sender allowlist via Graph API ## Current Maintainer Triage - Status: open - Normalized severity: medium - Assessment: Real in shipped v2026.3.28 MS Teams because Graph-fetched thread history bypasses sender allowlists, with unreleased mainline filtering fix. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version: `2026.3.31` - Vulnerable version range: `<=2026.3.28` - Patched versions: `>= 2026.3.31` - First stable tag containing the fix: `v2026.3.31` ## Fix Commit(s) - `5cca38084074fb5095aa11b6a59820d63e4937c9`

O3 Security · Impact-Aware SCA

Is GHSA-chfm-xgc4-47rj in your dependencies?

O3 detects GHSA-chfm-xgc4-47rj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works