Skip to content
Noroxi
OSV ecosystem advisory

GHSA-659f-22xc-98f2: OpenClaw hook transform path containment missed symlink-resolved escapes

High—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: openclaw (npm) 2026.2.22.

Low priority for now. Upgrade to openclaw (npm) 2026.2.22 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

## 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.

Published
Mar 3, 2026
Updated
Mar 4, 2026
EPSS
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-659f-22xc-98f2

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
npmopenclaw

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmopenclawbefore 2026.2.222026.2.22

Same product

npm: all records

Other highest-scoring records for the same primary product.

  • GHSA-943q-mwmv-hhvhOpenClaw: Gateway /tools/invoke tool escalation + ACP permission auto-approval
    35Monitor
  • GHSA-474h-prjg-mmw3OpenClaw: Sandboxed sessions_spawn(runtime="acp") bypassed sandbox inheritance and allowed host ACP initialization
    32Monitor
  • GHSA-56f2-hvwg-5743OpenClaw affected by SSRF in Image Tool Remote Fetch
    30Monitor

Published before and after this one in the same product

  • ← EarlierGHSA-w7j5-j98m-w679Mar 3, 2026 · OpenClaw has multiple E2E/test Dockerfiles that run all processes as root
    0Monitor
  • ← EarlierGHSA-gcj7-r3hg-m7w6Mar 3, 2026 · OpenClaw's voice-call Twilio replay dedupe now bound to authenticated webhook identity
    14Monitor
  • Later →GHSA-8mf7-vv8w-hjr2Mar 3, 2026 · OpenClaw's tools.exec.safeBins generic fallback allowed interpreter-style inline payload execution in allowlist mode
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:openclaw2026.2.22Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • GHSA-4cqv-h74h-93j40 days apartOpenClaw has a Discord `allowFrom` slug-collision authorization bypass
    26Monitor
  • GHSA-gcj7-r3hg-m7w60 days apartOpenClaw's voice-call Twilio replay dedupe now bound to authenticated webhook identity
    14Monitor
  • GHSA-2hm8-rqrm-xfjq0 days apartOpenClaw's owner-only gateway tool access checks were incomplete in specific authenticated DM flows
    0Monitor
  • GHSA-pfv7-rr5m-qmv60 days apartOpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint
    0Monitor

Not on record for this CVE: EPSS history · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None

CVSS vector

CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

osv

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records