GHSA-g34w-4xqq-h79m is a medium-severity (CVSS 6.5) CWE-284 vulnerability in openclaw. O3 Security confirms whether GHSA-g34w-4xqq-h79m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw iMessage group allowlist authorization inherited DM pairing-store identities
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
openclawnpmclawdbotnpmDescription
Summary
Under iMessage groupPolicy=allowlist, group authorization could be satisfied by sender identities coming from the DM pairing store, broadening DM trust into group contexts.
Details
Affected component: src/imessage/monitor/monitor-provider.ts.
Vulnerable logic derived effectiveGroupAllowFrom using both the static group allowlist and DM pairing-store identities (storeAllowFrom). This allowed a sender approved via DM pairing to satisfy group authorization in groups even if the sender/chat was not explicitly present in groupAllowFrom.
This weakens boundary separation between DM pairing and group allowlist authorization.
Affected Packages / Versions
openclaw(npm): affected<= 2026.2.13clawdbot(npm): affected<= 2026.1.24-3
Fix Commit(s)
openclaw/openclaw@872079d42fe105ece2900a1dd6ab321b92da2d59openclaw/openclaw@90d1e9cd71419168b2faa54a759b124a3eacfae7
Thanks @vincentkoc for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.14 |
| 📦npm | clawdbot | all versions | 2026.2.14 |
Detection & mitigation playbook
Open-source dependencyDetect
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.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g34w-4xqq-h79m 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-g34w-4xqq-h79m 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-g34w-4xqq-h79m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g34w-4xqq-h79m in your dependencies?
O3 detects GHSA-g34w-4xqq-h79m across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.