How severe is GHSA-g7cr-9h7q-4qxq?

No CVSS score has been assigned to GHSA-g7cr-9h7q-4qxq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g7cr-9h7q-4qxq?

GHSA-g7cr-9h7q-4qxq affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-g7cr-9h7q-4qxq?

Update openclaw to 2026.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7cr-9h7q-4qxq is resolved across your whole dependency graph.

How do I detect GHSA-g7cr-9h7q-4qxq 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-g7cr-9h7q-4qxq 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-g7cr-9h7q-4qxq?

O3 pinpoints whether GHSA-g7cr-9h7q-4qxq 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-g7cr-9h7q-4qxq actively exploited in the wild?

No public exploit code has been indexed for GHSA-g7cr-9h7q-4qxq 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-g7cr-9h7q-4qxq?

GHSA-g7cr-9h7q-4qxq is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g7cr-9h7q-4qxq published, and has it been updated?

GHSA-g7cr-9h7q-4qxq was published on March 12, 2026 and was last updated on April 6, 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-g7cr-9h7q-4qxq

Fix: openclaw/openclaw@88aee91

GHSA-g7cr-9h7q-4qxq is a CWE-863 vulnerability in openclaw. O3 Security confirms whether GHSA-g7cr-9h7q-4qxq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw's MS Teams sender allowlist bypass when route allowlist is configured and sender allowlist is empty

Also known asCVE-2026-34506

Published

Mar 12, 2026

Updated

Apr 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

OpenClaw's Microsoft Teams plugin widened group sender authorization when a team/channel route allowlist was configured but groupAllowFrom was empty. Before the fix, a matching route allowlist entry could cause the message handler to synthesize wildcard sender authorization for that route, allowing any sender in the matched team/channel to bypass the intended groupPolicy: "allowlist" sender check.

This does not affect default unauthenticated access, but it does weaken a documented Teams group authorization boundary and can allow unauthorized group senders to trigger replies in allowlisted Teams routes.

Affected Packages / Versions

Package: openclaw (npm)
Latest published vulnerable version: 2026.3.7
Affected range: <= 2026.3.7
Fixed in released version: 2026.3.8

Fix Commit(s)

88aee9161e0e6d32e810a25711e32a808a1777b2

Release Verification

Verified fixed in GitHub release v2026.3.8 published on March 9, 2026.
Verified npm view openclaw version resolves to 2026.3.8.
Verified the release contains the regression test covering the Teams route-allowlist sender-bypass case and that the test passes against the v2026.3.8 tree.

Thanks @zpbrent for reporting.

Affected Packages

1 total 1 fixed

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

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.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7cr-9h7q-4qxq 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-g7cr-9h7q-4qxq 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-g7cr-9h7q-4qxq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

OpenClaw's Microsoft Teams plugin widened group sender authorization when a team/channel route allowlist was configured but `groupAllowFrom` was empty. Before the fix, a matching route allowlist entry could cause the message handler to synthesize wildcard sender authorization for that route, allowing any sender in the matched team/channel to bypass the intended `groupPolicy: "allowlist"` sender check. This does not affect default unauthenticated access, but it does weaken a documented Teams group authorization boundary and can allow unauthorized group senders to trigger replies in allowlisted

O3 Security · Impact-Aware SCA

Is GHSA-g7cr-9h7q-4qxq in your dependencies?

O3 detects GHSA-g7cr-9h7q-4qxq 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