# GHSA-cjv3-m589-v3rx: OpenClaw has Canvas route hardening for mixed-trust deployments

> Attackers in mixed-trust or network-visible deployments could bypass canvas route authorization due to shared-IP fallbacks, requiring an upgrade to secure access boundaries.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2026

## What is GHSA-cjv3-m589-v3rx?

GHSA-cjv3-m589-v3rx is a missing authorization vulnerability in openclaw, published on 3 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

## Which versions are affected by GHSA-cjv3-m589-v3rx?

2 open source packages ship an affected version, including openclaw.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.2.21 |
| `openclaw` | npm | All versions | 2026.2.21 |

## How do I fix GHSA-cjv3-m589-v3rx?

Upgrade openclaw to 2026.2.21 or later.

## Is GHSA-cjv3-m589-v3rx being exploited?

There is no known exploitation of GHSA-cjv3-m589-v3rx in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-cjv3-m589-v3rx and fix it if it is affected.

What it is: GHSA-cjv3-m589-v3rx is a missing authorization vulnerability in openclaw, published on 3 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-cjv3-m589-v3rx in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.2.21
- openclaw (npm): affected all versions; fixed in 2026.2.21

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-cjv3-m589-v3rx/ (Markdown: https://insights.sbomify.com/GHSA-cjv3-m589-v3rx/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-cjv3-m589-v3rx

---
From sbomify Insights: https://insights.sbomify.com/GHSA-cjv3-m589-v3rx/
Summaries are generated and may contain mistakes; the official description above is the record.