GHSA-2hm8-rqrm-xfjq
OpenClaw's owner-only gateway tool access checks were incomplete in specific authenticated DM flows
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)
a40c10d3e24568b1e2947c104484be74bf66b8d22777d8ad91ef1e8a7c6f5b4b18f8507be7d029143d7ad1cfca4daaa84cd553e843e0e08fa6201349
OpenClaw thanks @Adam55A-code for reporting.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
What each source reports
GitHub Advisories Score used
OpenClaw's owner-only gateway tool access checks were incomplete in specific authenticated DM flows
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)
a40c10d3e24568b1e2947c104484be74bf66b8d22777d8ad91ef1e8a7c6f5b4b18f8507be7d029143d7ad1cfca4daaa84cd553e843e0e08fa6201349
OpenClaw thanks @Adam55A-code for reporting.
- Record
GHSA-2hm8-rqrm-xfjq- CVSS 4.0
- 4.8 Medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-269, CWE-863
- Updated
- 2026-11-02
OSV
OpenClaw's owner-only gateway tool access checks were incomplete in specific authenticated DM flows
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)
a40c10d3e24568b1e2947c104484be74bf66b8d22777d8ad91ef1e8a7c6f5b4b18f8507be7d029143d7ad1cfca4daaa84cd553e843e0e08fa6201349
OpenClaw thanks @Adam55A-code for reporting.
- Record
GHSA-2hm8-rqrm-xfjq- CVSS 4.0
- 4.8 Medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N - Weakness
- CWE-269, CWE-863
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
openclawnpm | before 2026.2.19 | 2026.2.19 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-2hm8-rqrm-xfjq is a medium vulnerability (CVSS 4.8) in openclaw, published March 3, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.19.
References
github.com/openclaw/openclaw/security/advisories/GHSA-2hm8-rqrm-xfjq