Summary
OpenClaw: Gateway operator.write Can Reach Admin-Class Channel Allowlist Persistence via chat.send
Fixed in OpenClaw 2026.3.24, the current shipping release.
The shared /allowlist command persists channel authorization config through writeConfigFile(...) but does not re-validate gateway client scopes for internal gateway callers. Because chat.send is intentionally reachable to operator.write callers and still creates a generic command-authorized internal context, an authenticated write-scoped gateway client can indirectly mutate channel allowFrom and groupAllowFrom policy that direct config.patch correctly reserves to operator.admin.
This is not just a generic code smell. The current code already shows the intended boundary by adding sink-side internal admin checks to shared /config and /plugins writes, but /allowlist was left behind.
Details
The gateway's documented scope split is clear:
chat.sendis a write-scoped action.- direct config mutation is an admin-scoped action.
The vulnerable path is:
- A gateway client authenticates with
operator.write. - The client calls
chat.send, which is intentionally allowed for that scope. chat.sendbuilds an internal message context withCommandAuthorized: trueand carriesGatewayClientScopesinto the reply pipeline.resolveCommandAuthorization(...)converts that internal message intoisAuthorizedSender=truein the common case where no strictercommands.allowFromoverride is configured./allowlist add|removeaccepts that generic command authorization and proceeds into its config-backed edit path.- The handler clones the parsed config, calls
plugin.allowlist.applyConfigEdit(...), validates the result, and persists it withwriteConfigFile(validated.config). - No sink-side check requires
operator.adminbefore the persistent write occurs.
That creates a direct control-plane mismatch:
config.patchrejects the same caller withmissing scope: operator.admin./allowlist add dm ...or/allowlist add group ...reached throughchat.sendcan still rewrite channel authorization state.
1) Add the Missing Sink-Side Internal Admin Check to /allowlist
Mirror the existing hardened pattern from /config and /plugins.
Before any config-backed /allowlist add|remove write, require:
operator.adminfor internal gateway channels
This should happen before plugin.allowlist.applyConfigEdit(...) and before writeConfigFile(...).
2) Keep Pairing-Store and Config-Write Policy Checks, but Do Not Treat Them as Scope Enforcement
configWrites policy and pairing-store behavior are useful secondary controls, but they do not replace the missing privilege check between operator.write and operator.admin.
Impact
- A gateway client intentionally limited to
operator.writecan persist first-party channel authorization policy. - The caller can widen DM or group allowlists for channels using the shared
/allowlistplumbing. - This weakens the repo's documented control-plane privilege split between ordinary write actions and admin-only persistent authorization mutation.
The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.
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-35621? CVE-2026-35621 is a high-severity improper privilege management vulnerability in openclaw (npm), affecting versions <= 2026.3.23. It is fixed in 2026.3.24. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- Which versions of openclaw are affected by CVE-2026-35621? openclaw (npm) versions <= 2026.3.23 is affected.
- Is there a fix for CVE-2026-35621? Yes. CVE-2026-35621 is fixed in 2026.3.24. Upgrade to this version or later.
- Is CVE-2026-35621 exploitable, and should I be worried? Whether CVE-2026-35621 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-35621 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-35621? Upgrade
openclawto 2026.3.24 or later.