How severe is GHSA-659f-22xc-98f2?

No CVSS score has been assigned to GHSA-659f-22xc-98f2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-659f-22xc-98f2?

GHSA-659f-22xc-98f2 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-659f-22xc-98f2?

Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-659f-22xc-98f2 is resolved across your whole dependency graph.

How do I detect GHSA-659f-22xc-98f2 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-659f-22xc-98f2 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-659f-22xc-98f2?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-659f-22xc-98f2 can be triaged on real exposure rather than presence alone.

Is GHSA-659f-22xc-98f2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-659f-22xc-98f2 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-659f-22xc-98f2 published, and has it been updated?

GHSA-659f-22xc-98f2 was published on March 3, 2026 and was last updated on March 4, 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-659f-22xc-98f2 — openclaw

Fix: openclaw/openclaw@f4dd057

GHSA-659f-22xc-98f2 is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw hook transform path containment missed symlink-resolved escapes

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, 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.7Mdownloads / week

Description

Vulnerability

Webhook transform modules were validated with lexical path checks only. A symlink under the allowed hooks transform tree could resolve outside the intended directory and be dynamically imported.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.21-2
Patched version (planned next release): 2026.2.22

Impact

When an attacker can cause a transform module path to reference a symlinked entry that resolves outside the trusted transform directory, the gateway may import and execute unintended JavaScript with gateway-process privileges.

Attack Preconditions

Hook transforms are enabled and reachable.
Attacker can influence transform path resolution (for example via privileged config access and/or writable filesystem path in the transform tree).
A symlink escape exists to attacker-controlled code.

Remediation

Enforce realpath-aware containment for existing path ancestors before dynamic import.
Keep lexical containment checks for traversal and absolute-path escapes.
Add regression coverage for:
- transform module symlink escape rejection,
- hooks.transformsDir symlink escape rejection,
- in-root symlink allow-case.

Fix Commit(s)

f4dd0577b055f77af783105bd65eae32f3d5e6a1

OpenClaw thanks @aether-ai-agent for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.22`npm install openclaw@2026.2.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-659f-22xc-98f2 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-659f-22xc-98f2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-659f-22xc-98f2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Vulnerability Webhook transform modules were validated with lexical path checks only. A symlink under the allowed hooks transform tree could resolve outside the intended directory and be dynamically imported. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.2.21-2` - Patched version (planned next release): `2026.2.22` ## Impact When an attacker can cause a transform module path to reference a symlinked entry that resolves outside the trusted transform directory, the gateway may import and execute unintended JavaScript with gateway-process privil

O3 Security · Impact-Aware SCA

Is GHSA-659f-22xc-98f2 in your dependencies?

O3 Security finds GHSA-659f-22xc-98f2 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works