How severe is GHSA-wppj-c6mr-83jj?

GHSA-wppj-c6mr-83jj has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-wppj-c6mr-83jj?

GHSA-wppj-c6mr-83jj affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-wppj-c6mr-83jj?

Update openclaw to 2026.4.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wppj-c6mr-83jj is resolved across your whole dependency graph.

How do I detect GHSA-wppj-c6mr-83jj 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-wppj-c6mr-83jj 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-wppj-c6mr-83jj?

O3 pinpoints whether GHSA-wppj-c6mr-83jj 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-wppj-c6mr-83jj actively exploited in the wild?

No public exploit code has been indexed for GHSA-wppj-c6mr-83jj 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-wppj-c6mr-83jj published, and has it been updated?

GHSA-wppj-c6mr-83jj was published on May 4, 2026 and was last updated on May 12, 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

GHSA-wppj-c6mr-83jj

MEDIUM

GHSA-wppj-c6mr-83jj is a medium-severity (CVSS 5.3) vulnerability in openclaw. O3 Security confirms whether GHSA-wppj-c6mr-83jj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: OpenShell FS bridge writes stay pinned to the sandbox mount root

Also known asCVE-2026-44112

Published

May 4, 2026

Updated

May 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

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

openclawnpm

3.1Mdownloads / week

Description

Summary

OpenShell FS bridge writes stay pinned to the sandbox mount root

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.4.21
Fixed version: 2026.4.22

Impact

A time-of-check/time-of-use race around OpenShell sandbox filesystem writes could let a symlink swap redirect a write outside the intended local mount root.

Fix

OpenShell write paths now validate the canonical target against the mount root, reject unsafe symlink parents and symlink leaves for writes, and use root-scoped write helpers before syncing to the remote sandbox.

Fix Commit(s)

7be82d4fd1193bcb7e44ee38838f00bf924ffa76

Verification

The fix commit is contained in the public v2026.4.22 tag.
[email protected] is published on npm and the compiled package contains the fix.
Focused regression coverage for this path passed before publication.

Thanks @VladimirEliTokarev for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.4.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.4.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wppj-c6mr-83jj 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-wppj-c6mr-83jj 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-wppj-c6mr-83jj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary OpenShell FS bridge writes stay pinned to the sandbox mount root ## Affected Packages / Versions - Package: openclaw (npm) - Affected versions: <= 2026.4.21 - Fixed version: 2026.4.22 ## Impact A time-of-check/time-of-use race around OpenShell sandbox filesystem writes could let a symlink swap redirect a write outside the intended local mount root. ## Fix OpenShell write paths now validate the canonical target against the mount root, reject unsafe symlink parents and symlink leaves for writes, and use root-scoped write helpers before syncing to the remote sandbox. ## Fix Commit

O3 Security · Impact-Aware SCA

Is GHSA-wppj-c6mr-83jj in your dependencies?

O3 detects GHSA-wppj-c6mr-83jj 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