How severe is GHSA-v3qc-wrwx-j3pw?

No CVSS score has been assigned to GHSA-v3qc-wrwx-j3pw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v3qc-wrwx-j3pw?

GHSA-v3qc-wrwx-j3pw affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-v3qc-wrwx-j3pw?

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

How do I detect GHSA-v3qc-wrwx-j3pw 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-v3qc-wrwx-j3pw if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-v3qc-wrwx-j3pw actively exploited in the wild?

No public exploit code has been indexed for GHSA-v3qc-wrwx-j3pw 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-v3qc-wrwx-j3pw?

GHSA-v3qc-wrwx-j3pw has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th 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-v3qc-wrwx-j3pw?

GHSA-v3qc-wrwx-j3pw is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v3qc-wrwx-j3pw published, and has it been updated?

GHSA-v3qc-wrwx-j3pw was published on April 3, 2026 and was last updated on July 8, 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: Agentic Consent Bypass — LLM Agent Can Silently Disable Exec Approval via `config.patch`GHSA-v3qc-wrwx-j3pw

Fix: openclaw/openclaw@76411b2

GHSA-v3qc-wrwx-j3pw is a CWE-862 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Also known asCVE-2026-41349

Published

Apr 3, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 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-v3qc-wrwx-j3pw.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% 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.4Mdownloads / week

Description

Summary

Agentic Consent Bypass: LLM Agent Can Silently Disable Exec Approval via config.patch

Current Maintainer Triage

Status: open
Normalized severity: high
Assessment: Maintainers accepted this issue, fixed it in 76411b2afc4ae721e36c12e0ea24fd23e2fed61e on 2026-03-27, and that fix shipped in v2026.3.28, so normalize it as a fixed released draft rather than a close-by-trust-model call.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version: 2026.3.31
Vulnerable version range: <=2026.3.24
Patched versions: >= 2026.3.28
First stable tag containing the fix: v2026.3.28

Fix Commit(s)

76411b2afc4ae721e36c12e0ea24fd23e2fed61e — 2026-03-27T09:42:15Z

OpenClaw thanks @YLChen-007 for reporting.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.3.28

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.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v3qc-wrwx-j3pw is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

## Summary Agentic Consent Bypass: LLM Agent Can Silently Disable Exec Approval via `config.patch` ## Current Maintainer Triage - Status: open - Normalized severity: high - Assessment: Maintainers accepted this issue, fixed it in 76411b2afc4ae721e36c12e0ea24fd23e2fed61e on 2026-03-27, and that fix shipped in v2026.3.28, so normalize it as a fixed released draft rather than a close-by-trust-model call. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published npm version: `2026.3.31` - Vulnerable version range: `<=2026.3.24` - Patched versions: `>= 2026.3.28` - First stab

O3 Security · Impact-Aware SCA

Is GHSA-v3qc-wrwx-j3pw in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works