How severe is GHSA-vhwf-4x96-vqx2?

No CVSS score has been assigned to GHSA-vhwf-4x96-vqx2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vhwf-4x96-vqx2?

GHSA-vhwf-4x96-vqx2 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-vhwf-4x96-vqx2?

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

How do I detect GHSA-vhwf-4x96-vqx2 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-vhwf-4x96-vqx2 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-vhwf-4x96-vqx2?

O3 pinpoints whether GHSA-vhwf-4x96-vqx2 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-vhwf-4x96-vqx2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vhwf-4x96-vqx2 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-vhwf-4x96-vqx2?

GHSA-vhwf-4x96-vqx2 is classified as CWE-367 (CWE-367). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vhwf-4x96-vqx2 published, and has it been updated?

GHSA-vhwf-4x96-vqx2 was published on March 12, 2026 and was last updated on April 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-vhwf-4x96-vqx2: openclaw

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

3.2Mdownloads / week

Description

OpenClaw's skills download installer validated the intended per-skill tools root lexically, but later reused that mutable path while downloading and copying the archive into place. If a local attacker could rebind that tools-root path between validation and the final write, the installer could be redirected to write outside the intended tools directory.

The fix pins the canonical per-skill tools root immediately after validation and derives later download/copy paths from that canonical root, so rebinding the lexical path fails closed instead of redirecting the write.

Affected Packages / Versions

Package: openclaw (npm)
Latest published vulnerable version: 2026.3.7
Affected range: <= 2026.3.7
Fixed in released version: 2026.3.8

Fix Commit(s)

9abf014f3502009faf9c73df5ca2cff719e54639

Release Verification

Verified fixed in GitHub release v2026.3.8 published on March 9, 2026.
Verified npm view openclaw version resolves to 2026.3.8.
Verified the release contains the regression test covering tools-root rebinding and that the test passes against the v2026.3.8 tree.

Thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

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

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.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhwf-4x96-vqx2 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-vhwf-4x96-vqx2 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-vhwf-4x96-vqx2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

OpenClaw's skills download installer validated the intended per-skill tools root lexically, but later reused that mutable path while downloading and copying the archive into place. If a local attacker could rebind that tools-root path between validation and the final write, the installer could be redirected to write outside the intended tools directory. The fix pins the canonical per-skill tools root immediately after validation and derives later download/copy paths from that canonical root, so rebinding the lexical path fails closed instead of redirecting the write. ## Affected Packages / V

O3 Security · Impact-Aware SCA

Is GHSA-vhwf-4x96-vqx2 in your dependencies?

O3 detects GHSA-vhwf-4x96-vqx2 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

GHSA-vhwf-4x96-vqx2