Summary
OpenClaw: Bundled MCP/LSP tools could bypass configured tool policy
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
< 2026.4.20 - Patched version:
2026.4.20
Release
Fixed in OpenClaw 2026.4.20.
Impact
Bundled MCP and LSP tools could be appended to the agent's effective tool set after the normal tool-policy pipeline had already filtered core tools. If an operator configured a restrictive policy, such as a tool profile, explicit allow/deny list, owner-only tool restriction, sandbox tool policy, or subagent tool policy, a bundled MCP/LSP tool could remain available even though the same policy would have denied it.
The issue required a configured bundled MCP or LSP tool source and an operator policy that should have restricted that tool. This was a local agent policy-enforcement bypass, not an unauthenticated remote gateway compromise. Severity is medium.
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
OpenClaw now applies a final effective tool policy pass to bundled MCP/LSP tools before merging them into the tool set used by normal runs and compaction. The pass covers profile policy, provider profile policy, global/agent/group policies, owner-only filtering, sandbox tool policy, and subagent tool policy.
Fix commit:
0e7a992d3f3155199c1acc2dd9a53c5b3a4d3ada
Frequently Asked Questions
- What is GHSA-QRP5-GFW2-GXV4? GHSA-QRP5-GFW2-GXV4 is a medium-severity missing authorization vulnerability in openclaw (npm), affecting versions < 2026.4.20. It is fixed in 2026.4.20. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of openclaw are affected by GHSA-QRP5-GFW2-GXV4? openclaw (npm) versions < 2026.4.20 is affected.
- Is there a fix for GHSA-QRP5-GFW2-GXV4? Yes. GHSA-QRP5-GFW2-GXV4 is fixed in 2026.4.20. Upgrade to this version or later.
- Is GHSA-QRP5-GFW2-GXV4 exploitable, and should I be worried? Whether GHSA-QRP5-GFW2-GXV4 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-QRP5-GFW2-GXV4 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-QRP5-GFW2-GXV4? Upgrade
openclawto 2026.4.20 or later.