How severe is GHSA-4qwc-c7g9-4xcw?

No CVSS score has been assigned to GHSA-4qwc-c7g9-4xcw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4qwc-c7g9-4xcw?

GHSA-4qwc-c7g9-4xcw affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-4qwc-c7g9-4xcw?

Update openclaw to 2026.3.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4qwc-c7g9-4xcw is resolved across your whole dependency graph.

How do I detect GHSA-4qwc-c7g9-4xcw in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-4qwc-c7g9-4xcw 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-4qwc-c7g9-4xcw?

O3 pinpoints whether GHSA-4qwc-c7g9-4xcw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4qwc-c7g9-4xcw actively exploited in the wild?

No public exploit code has been indexed for GHSA-4qwc-c7g9-4xcw 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 type of vulnerability is GHSA-4qwc-c7g9-4xcw?

GHSA-4qwc-c7g9-4xcw is classified as CWE-789 (CWE-789), CWE-770 (CWE-770). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4qwc-c7g9-4xcw published, and has it been updated?

GHSA-4qwc-c7g9-4xcw was published on March 26, 2026 and was last updated on April 10, 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-4qwc-c7g9-4xcw

Fix: openclaw/openclaw@630f147

GHSA-4qwc-c7g9-4xcw is a CWE-789 vulnerability in openclaw. O3 Security confirms whether GHSA-4qwc-c7g9-4xcw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Remote media error responses could trigger unbounded memory allocation before failure

Also known asCVE-2026-35633

Published

Mar 26, 2026

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.2Mdownloads / week

Description

Summary

Remote media HTTP error bodies were read without a hard size cap before failure handling, allowing unbounded allocation on error responses.

Affected Packages / Versions

Package: openclaw (npm)
Affected: < 2026.3.22
Fixed: >= 2026.3.22
Latest released tag checked: v2026.3.23-2 (630f1479c44f78484dfa21bb407cbe6f171dac87)
Latest published npm version checked: 2026.3.23-2

Fix Commit(s)

81445a901091a5d27ef0b56fceedbe4724566438

Release Status

The fix shipped in v2026.3.22 and remains present in v2026.3.23 and v2026.3.23-2.

Code-Level Confirmation

src/media/fetch.ts now routes non-2xx failures through bounded prefix reads instead of buffering the whole error body.
src/media/read-response-with-limit.ts enforces capped reads and truncates oversized snippets before surfacing failure text.

OpenClaw thanks @YLChen-007 for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.3.22

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.3.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4qwc-c7g9-4xcw 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 pinpoints whether GHSA-4qwc-c7g9-4xcw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4qwc-c7g9-4xcw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Remote media HTTP error bodies were read without a hard size cap before failure handling, allowing unbounded allocation on error responses. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: < 2026.3.22 - Fixed: >= 2026.3.22 - Latest released tag checked: `v2026.3.23-2` (`630f1479c44f78484dfa21bb407cbe6f171dac87`) - Latest published npm version checked: `2026.3.23-2` ## Fix Commit(s) - `81445a901091a5d27ef0b56fceedbe4724566438` ## Release Status The fix shipped in `v2026.3.22` and remains present in `v2026.3.23` and `v2026.3.23-2`. ## Code-Level Confirmation

O3 Security · Impact-Aware SCA

Is GHSA-4qwc-c7g9-4xcw in your dependencies?

O3 detects GHSA-4qwc-c7g9-4xcw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works