Summary
OpenClaw: Gateway agent /reset exposes admin session reset to operator.write callers
Before v2026.3.23, the Gateway agent RPC accepted /reset and /new for callers with only operator.write, even though the direct sessions.reset RPC correctly requires operator.admin.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
< 2026.3.23 - Fixed:
>= 2026.3.23 - Latest released tag checked:
v2026.3.23-2(630f1479c44f78484dfa21bb407cbe6f171dac87) - Latest published npm version checked:
2026.3.23-2
Root Cause
The vulnerable path lived in src/gateway/server-methods/agent.ts. A /reset or /new message with an explicit sessionKey reached performGatewaySessionReset(...) without enforcing the same operator.admin guard used by sessions.reset.
Fix Commit(s)
50f6a2f136fed85b58548a38f7a3dbb98d2cd1a0,fix(gateway): require admin for agent session reset
Release Status
The fix commit is contained in released tags v2026.3.23 and v2026.3.23-2. The latest shipped tag and npm release both include the fix.
Code-Level Confirmation
src/gateway/server-methods/agent.tsnow rejects/resetand/newfor callers that do not haveoperator.adminbefore callingperformGatewaySessionReset(...).src/gateway/server-methods/agent.test.tscontains the regression testrejects /reset for write-scoped gateway callers.
Thanks @smaeljaish771 for reporting.
Impact
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-35660? CVE-2026-35660 is a high-severity missing authorization vulnerability in openclaw (npm), affecting versions < 2026.3.23. It is fixed in 2026.3.23. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of openclaw are affected by CVE-2026-35660? openclaw (npm) versions < 2026.3.23 is affected.
- Is there a fix for CVE-2026-35660? Yes. CVE-2026-35660 is fixed in 2026.3.23. Upgrade to this version or later.
- Is CVE-2026-35660 exploitable, and should I be worried? Whether CVE-2026-35660 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-35660 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-35660? Upgrade
openclawto 2026.3.23 or later.