Openclaw cli: OpenClaw's owner-only gateway tool access checks were incomplete in specific authenticated DM flows
Affects openclaw-cliSource GCVE Database
CVSS 4.8 Medium : upgrade to 2026.7.1 when convenient.
Data as of 17 Nov 2026, 19:05 UTC
- Patch
- Available – fixed in 2026.7.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NWhat to do
Upgrade openclaw-cli to 2026.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in OpenClaw CLI version 2026.2.19 that refactors gateway method scope mapping and centralizes owner-only enforcement. Users should upgrade to version 2026.2.19 or later to remediate this issue. No additional mitigation actions are required beyond applying the official fix.
Description
OpenClaw CLI had an issue where authenticated non-owner users in direct message sessions could invoke certain owner-only gateway actions through a narrow tool invocation path. This vulnerability does not allow unauthenticated access or direct code execution. The root cause was inconsistent enforcement of owner-only access controls, relying on tool-name checks rather than comprehensive metadata-driven scopes. The issue affects openclaw versions up to 2026.2.17 and was fixed in version 2026.2.19 by refactoring scope mappings and centralizing owner-only enforcement.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-2hm8-rqrm-xfjq (opens in a new tab)
- github.com/openclaw/openclaw/commit/2777d8ad91ef1e8a7c6f5b4b18f8507be7d02914 (opens in a new tab)
- github.com/openclaw/openclaw/commit/3d7ad1cfca4daaa84cd553e843e0e08fa6201349 (opens in a new tab)
- github.com/openclaw/openclaw/commit/a40c10d3e24568b1e2947c104484be74bf66b8d2 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)