Summary
OpenClaw has Canvas route hardening for mixed-trust deployments
This advisory tracks a defense-in-depth hardening for canvas routes. In mixed-trust or network-visible deployments, prior canvas auth/fallback behavior could broaden access beyond intended boundaries.
Deployment Context
OpenClaw’s default model is trusted host + loopback-first access. Some operators intentionally expose canvas routes on LAN/tailnet. This update is aimed at those broader deployment patterns.
What Changed
- Require explicit token or session-capability authorization for canvas routes.
- Remove shared-IP fallback paths for canvas access.
- Tighten bind/fallback behavior to fail closed.
Affected Packages / Versions
- Package:
openclaw(npm) - Vulnerable:
<= 2026.2.19-2 - Patched:
2026.2.21(next release target)
Fix Commit(s)
c45f3c5b004c8d63dc0e282e2176f8c9355d24f108a7967936cfc0b2af6b27ec1f9272542648ad6c
Thanks @NucleiAv for reporting.
Impact
Risk was highest in non-loopback or mixed-trust environments. In strict single-operator trusted-host setups, practical exposure is lower.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
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 GHSA-CJV3-M589-V3RX? GHSA-CJV3-M589-V3RX is a medium-severity cross-site scripting (XSS) vulnerability in openclaw (npm), affecting versions < 2026.2.21. It is fixed in 2026.2.21. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of openclaw are affected by GHSA-CJV3-M589-V3RX? openclaw (npm) versions < 2026.2.21 is affected.
- Is there a fix for GHSA-CJV3-M589-V3RX? Yes. GHSA-CJV3-M589-V3RX is fixed in 2026.2.21. Upgrade to this version or later.
- Is GHSA-CJV3-M589-V3RX exploitable, and should I be worried? Whether GHSA-CJV3-M589-V3RX 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-CJV3-M589-V3RX 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-CJV3-M589-V3RX? Upgrade
openclawto 2026.2.21 or later.