How severe is GHSA-2hm8-rqrm-xfjq?

No CVSS score has been assigned to GHSA-2hm8-rqrm-xfjq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2hm8-rqrm-xfjq?

GHSA-2hm8-rqrm-xfjq affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-2hm8-rqrm-xfjq?

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

How do I detect GHSA-2hm8-rqrm-xfjq 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-2hm8-rqrm-xfjq 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-2hm8-rqrm-xfjq?

O3 pinpoints whether GHSA-2hm8-rqrm-xfjq 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-2hm8-rqrm-xfjq actively exploited in the wild?

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

GHSA-2hm8-rqrm-xfjq was published on March 3, 2026 and was last updated on March 4, 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-2hm8-rqrm-xfjq

OpenClaw's owner-only gateway tool access checks were incomplete in specific authenticated DM flows

Published

Mar 3, 2026

Updated

Mar 4, 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

In authenticated non-owner DM sessions, a narrow tool-invocation path could reach broader-than-intended owner-only gateway actions.

Impact

This requires an authenticated non-owner sender in a DM session and a specific tool invocation path. No unauthenticated access is involved, and this does not provide direct code execution by itself.

Root Cause

Some gateway call paths were still using broader default scopes instead of method-level least-privilege scopes.
Owner-only enforcement depended on tool-name checks and was not consistently metadata-driven across all call paths.

Affected Packages / Versions

Package: openclaw (npm)
Affected: <= 2026.2.17 (latest published npm version as of February 19, 2026)
Patched: 2026.2.19

Remediation

Refactored gateway method scope mapping to a data-driven table and added guard tests to ensure all exposed core gateway methods stay classified.
Centralized owner-only enforcement in tool policy wrappers and tool metadata.
Marked owner-only tools explicitly (cron, gateway, whatsapp_login) and removed duplicated per-tool owner checks.
Refactored gateway call path internals into smaller helpers while preserving behavior and coverage.

Fix Commit(s)

a40c10d3e24568b1e2947c104484be74bf66b8d2
2777d8ad91ef1e8a7c6f5b4b18f8507be7d02914
3d7ad1cfca4daaa84cd553e843e0e08fa6201349

OpenClaw thanks @Adam55A-code for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Summary In authenticated non-owner DM sessions, a narrow tool-invocation path could reach broader-than-intended owner-only gateway actions. ## Impact This requires an authenticated non-owner sender in a DM session and a specific tool invocation path. No unauthenticated access is involved, and this does not provide direct code execution by itself. ## Root Cause - Some gateway call paths were still using broader default scopes instead of method-level least-privilege scopes. - Owner-only enforcement depended on tool-name checks and was not consistently metadata-driven across all call path

O3 Security · Impact-Aware SCA

Is GHSA-2hm8-rqrm-xfjq in your dependencies?

O3 detects GHSA-2hm8-rqrm-xfjq 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