Skip to content
Fencer Intel
medium —

GHSA-cjv3-m589-v3rx json

OpenClaw has Canvas route hardening for mixed-trust deployments

published 8mo ago modified 8mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

## Summary 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.

## Impact Risk was highest in non-loopback or mixed-trust environments. In strict single-operator trusted-host setups, practical exposure is lower.

## Affected Packages / Versions - Package: `openclaw` (npm) - Vulnerable: `<= 2026.2.19-2` - Patched: `2026.2.21` (next release target)

## Fix Commit(s) - `c45f3c5b004c8d63dc0e282e2176f8c9355d24f1` - `08a7967936cfc0b2af6b27ec1f9272542648ad6c`

Thanks @NucleiAv for reporting.

Patch / fix

  • npm openclaw 2026.2.21

Is GHSA-cjv3-m589-v3rx in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm openclaw
<2026.2.21
2026.2.21

Classification

Weakness
  • CWE-1021 Improper Restriction of Rendered UI Layers or Frames
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of openclaw/openclaw published their own advisory on GitHub. Reviewed sources take precedence over it.