How severe is GHSA-m69h-jm2f-2pv8?

No CVSS score has been assigned to GHSA-m69h-jm2f-2pv8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m69h-jm2f-2pv8?

GHSA-m69h-jm2f-2pv8 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-m69h-jm2f-2pv8?

Update openclaw to 2026.3.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m69h-jm2f-2pv8 is resolved across your whole dependency graph.

How do I detect GHSA-m69h-jm2f-2pv8 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-m69h-jm2f-2pv8 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-m69h-jm2f-2pv8?

O3 pinpoints whether GHSA-m69h-jm2f-2pv8 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-m69h-jm2f-2pv8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m69h-jm2f-2pv8 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-m69h-jm2f-2pv8 published, and has it been updated?

GHSA-m69h-jm2f-2pv8 was published on March 13, 2026 and was last updated on March 13, 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-m69h-jm2f-2pv8

OpenClaw: Feishu reaction events could bypass group authorization and mention gating

Published

Mar 13, 2026

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

Summary

A Feishu reaction-originated synthetic event could misclassify a group conversation as p2p when the inbound reaction payload omitted chat_type. Authorization and mention-gating logic keyed off that incorrect chat type and evaluated the event as a direct message instead of a group message.

Impact

This could bypass groupAllowFrom and requireMention protections for reaction-derived events in Feishu group chats.

Affected versions

openclaw <= 2026.3.11

Patch

Fixed in openclaw 2026.3.12. Reaction events now preserve the correct group context before authorization and mention-gate evaluation. Users should update to 2026.3.12 or later.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

### Summary A Feishu reaction-originated synthetic event could misclassify a group conversation as `p2p` when the inbound reaction payload omitted `chat_type`. Authorization and mention-gating logic keyed off that incorrect chat type and evaluated the event as a direct message instead of a group message. ### Impact This could bypass `groupAllowFrom` and `requireMention` protections for reaction-derived events in Feishu group chats. ### Affected versions `openclaw` `<= 2026.3.11` ### Patch Fixed in `openclaw` `2026.3.12`. Reaction events now preserve the correct group context before auth

O3 Security · Impact-Aware SCA

Is GHSA-m69h-jm2f-2pv8 in your dependencies?

O3 detects GHSA-m69h-jm2f-2pv8 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