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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m69h-jm2f-2pv8 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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.

What is the EPSS score for GHSA-m69h-jm2f-2pv8?

GHSA-m69h-jm2f-2pv8 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m69h-jm2f-2pv8?

GHSA-m69h-jm2f-2pv8 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-m69h-jm2f-2pv8 published, and has it been updated?

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

Not in CISA KEV

OpenClaw: Feishu reaction events could bypass group authorization and mention gatingGHSA-m69h-jm2f-2pv8

Fix: openclaw/openclaw#44088

GHSA-m69h-jm2f-2pv8 is a CWE-863 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-32924

Published

Mar 13, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m69h-jm2f-2pv8.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg 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

2.5Mdownloads / 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`npm install openclaw@2026.3.12`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.3.12

range

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.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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works