How severe is GHSA-2qrv-rc5x-2g2h?

No CVSS score has been assigned to GHSA-2qrv-rc5x-2g2h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2qrv-rc5x-2g2h?

GHSA-2qrv-rc5x-2g2h affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-2qrv-rc5x-2g2h?

Update openclaw to 2026.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2qrv-rc5x-2g2h is resolved across your whole dependency graph.

How do I detect GHSA-2qrv-rc5x-2g2h 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-2qrv-rc5x-2g2h 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.

Is GHSA-2qrv-rc5x-2g2h actively exploited in the wild?

No public exploit code has been indexed for GHSA-2qrv-rc5x-2g2h 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.

What is the EPSS score for GHSA-2qrv-rc5x-2g2h?

GHSA-2qrv-rc5x-2g2h has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 3th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2qrv-rc5x-2g2h?

GHSA-2qrv-rc5x-2g2h is classified as CWE-829 (CWE-829). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2qrv-rc5x-2g2h published, and has it been updated?

GHSA-2qrv-rc5x-2g2h was published on April 7, 2026 and was last updated on April 20, 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

OpenClaw: Untrusted workspace channel shadows could execute during built-in channel setupGHSA-2qrv-rc5x-2g2h

Fix: openclaw/openclaw@53c29df

GHSA-2qrv-rc5x-2g2h is a CWE-829 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-41295

Published

Apr 7, 2026

Updated

Apr 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2qrv-rc5x-2g2h.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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

2.5Mdownloads / week

Description

Summary

Before OpenClaw 2026.4.2, built-in channel setup and login could resolve an untrusted workspace channel shadow before the plugin was explicitly trusted. A malicious workspace plugin that claimed a bundled channel id could execute during channel setup even while still disabled.

Impact

A cloned workspace could turn channel setup for a built-in channel into unintended in-process code execution from an untrusted workspace plugin. This bypassed the intended workspace-plugin trust boundary during setup and login.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.4.1
Patched versions: >= 2026.4.2
Latest published npm version: 2026.4.1

Fix Commit(s)

53c29df2a9eb242a70d0ff29f3d1e67c8d6801f0 — ignore untrusted workspace channel shadows during setup resolution

Release Process Note

The fix is present on main and is staged for OpenClaw 2026.4.2. Publish this advisory after the 2026.4.2 npm release is live.

Thanks @zpbrent for reporting.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.4.2

range

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.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2qrv-rc5x-2g2h 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.

Frequently Asked Questions

## Summary Before OpenClaw 2026.4.2, built-in channel setup and login could resolve an untrusted workspace channel shadow before the plugin was explicitly trusted. A malicious workspace plugin that claimed a bundled channel id could execute during channel setup even while still disabled. ## Impact A cloned workspace could turn channel setup for a built-in channel into unintended in-process code execution from an untrusted workspace plugin. This bypassed the intended workspace-plugin trust boundary during setup and login. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affect

O3 Security · Impact-Aware SCA

Is GHSA-2qrv-rc5x-2g2h in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works