Summary
OpenClaw's authorization mismatch allowed write-scope agent runs to reach owner-only tools
An authorization mismatch allowed authenticated callers with operator.write access to invoke owner-only tool surfaces (gateway, cron) through agent runs in scoped-token deployments.
Affected and Patched Versions
- Affected:
<= 2026.2.26 - Patched:
2026.3.1
Impact
On affected deployments, write-scoped callers could perform control-plane actions beyond intended write scope.
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
Owner-only gating is now enforced consistently for owner-only tool surfaces during agent execution, and tool scope classification was tightened to remove the privilege mismatch.
Frequently Asked Questions
- What is GHSA-JR6X-2Q95-FH2G? GHSA-JR6X-2Q95-FH2G is a high-severity improper privilege management vulnerability in openclaw (npm), affecting versions < 2026.3.1. It is fixed in 2026.3.1. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- Which versions of openclaw are affected by GHSA-JR6X-2Q95-FH2G? openclaw (npm) versions < 2026.3.1 is affected.
- Is there a fix for GHSA-JR6X-2Q95-FH2G? Yes. GHSA-JR6X-2Q95-FH2G is fixed in 2026.3.1. Upgrade to this version or later.
- Is GHSA-JR6X-2Q95-FH2G exploitable, and should I be worried? Whether GHSA-JR6X-2Q95-FH2G 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 GHSA-JR6X-2Q95-FH2G 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 GHSA-JR6X-2Q95-FH2G? Upgrade
openclawto 2026.3.1 or later.