How severe is GHSA-cjv3-m589-v3rx?

No CVSS score has been assigned to GHSA-cjv3-m589-v3rx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cjv3-m589-v3rx?

GHSA-cjv3-m589-v3rx affects the following packages: openclaw (npm). Ecosystems affected: npm.

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

Update openclaw to 2026.2.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cjv3-m589-v3rx is resolved across your whole dependency graph.

How do I detect GHSA-cjv3-m589-v3rx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cjv3-m589-v3rx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-cjv3-m589-v3rx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cjv3-m589-v3rx can be triaged on real exposure rather than presence alone.

Is GHSA-cjv3-m589-v3rx actively exploited in the wild?

No public exploit code has been indexed for GHSA-cjv3-m589-v3rx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-cjv3-m589-v3rx published, and has it been updated?

GHSA-cjv3-m589-v3rx was published on March 3, 2026 and was last updated on March 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-cjv3-m589-v3rx — openclaw

Fix: openclaw/openclaw@08a7967

GHSA-cjv3-m589-v3rx is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw has Canvas route hardening for mixed-trust deployments

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

4.1Mdownloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.21`npm install openclaw@2026.2.21`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cjv3-m589-v3rx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cjv3-m589-v3rx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cjv3-m589-v3rx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-cjv3-m589-v3rx in your dependencies?

O3 Security finds GHSA-cjv3-m589-v3rx across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works