How severe is GHSA-mw7w-g3mg-xqm7?

No CVSS score has been assigned to GHSA-mw7w-g3mg-xqm7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mw7w-g3mg-xqm7?

GHSA-mw7w-g3mg-xqm7 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-mw7w-g3mg-xqm7?

No patched version of openclaw has shipped for GHSA-mw7w-g3mg-xqm7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-mw7w-g3mg-xqm7 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-mw7w-g3mg-xqm7 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-mw7w-g3mg-xqm7?

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

Is GHSA-mw7w-g3mg-xqm7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mw7w-g3mg-xqm7 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-mw7w-g3mg-xqm7?

GHSA-mw7w-g3mg-xqm7 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th 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-mw7w-g3mg-xqm7?

GHSA-mw7w-g3mg-xqm7 is classified as CWE-288 (CWE-288). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mw7w-g3mg-xqm7 published, and has it been updated?

GHSA-mw7w-g3mg-xqm7 was published on March 27, 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

GHSA-mw7w-g3mg-xqm7 — openclaw

Fix: openclaw/openclaw@f8c9863

GHSA-mw7w-g3mg-xqm7 is a CWE-288 vulnerability in openclaw. No vendor fix is recorded yet; mitigation options are listed below.

OpenClaw: BlueBubbles Group Reactions Bypass requireMention and Still Enqueue Agent-Visible System Events

Also known asCVE-2026-35642

Published

Mar 27, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-mw7w-g3mg-xqm7.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs10th percentile — riskier than 10% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

3.1Mdownloads / week

Description

Summary

BlueBubbles Group Reactions Bypass requireMention and Still Enqueue Agent-Visible System Events

Affected Packages / Versions

Package: openclaw
Affected versions: <= 2026.3.24
First patched version: 2026.3.25
Latest published npm version at verification time: 2026.3.24

Details

BlueBubbles group reaction events previously bypassed requireMention and still enqueued agent-visible system events in groups that were supposed to stay mention-gated. Commit f8c98630785288cc1f1d0893503ef3b653a3cede applies the reaction path to the same mention gate as normal group messages.

Verified vulnerable on tag v2026.3.24 and fixed on main by commit f8c98630785288cc1f1d0893503ef3b653a3cede.

Fix Commit(s)

f8c98630785288cc1f1d0893503ef3b653a3cede

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	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.
Remediation status
No patched version of openclaw has shipped for GHSA-mw7w-g3mg-xqm7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-mw7w-g3mg-xqm7 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

## Summary BlueBubbles Group Reactions Bypass requireMention and Still Enqueue Agent-Visible System Events ## Affected Packages / Versions - Package: `openclaw` - Affected versions: `<= 2026.3.24` - First patched version: `2026.3.25` - Latest published npm version at verification time: `2026.3.24` ## Details BlueBubbles group reaction events previously bypassed `requireMention` and still enqueued agent-visible system events in groups that were supposed to stay mention-gated. Commit `f8c98630785288cc1f1d0893503ef3b653a3cede` applies the reaction path to the same mention gate as normal grou

O3 Security · Impact-Aware SCA

Is GHSA-mw7w-g3mg-xqm7 in your dependencies?

O3 Security finds GHSA-mw7w-g3mg-xqm7 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