How severe is GHSA-cr8r-7g2h-6wr6?

No CVSS score has been assigned to GHSA-cr8r-7g2h-6wr6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cr8r-7g2h-6wr6?

GHSA-cr8r-7g2h-6wr6 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-cr8r-7g2h-6wr6?

Update openclaw to 2026.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cr8r-7g2h-6wr6 is resolved across your whole dependency graph.

How do I detect GHSA-cr8r-7g2h-6wr6 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-cr8r-7g2h-6wr6 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.

Is GHSA-cr8r-7g2h-6wr6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cr8r-7g2h-6wr6 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 is the EPSS score for GHSA-cr8r-7g2h-6wr6?

GHSA-cr8r-7g2h-6wr6 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cr8r-7g2h-6wr6?

GHSA-cr8r-7g2h-6wr6 is classified as CWE-61 (CWE-61). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cr8r-7g2h-6wr6 published, and has it been updated?

GHSA-cr8r-7g2h-6wr6 was published on May 5, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

OpenClaw 2026.3.22 < 2026.4.5 - Symlink Traversal in…

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cr8r-7g2h-6wr6.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.17%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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.9Mdownloads / week

Description

OpenClaw versions 2026.3.22 before 2026.4.5 contain a symlink traversal vulnerability in remote marketplace repository path handling that allows attackers to escape the expected repository root. Attackers can exploit this by providing crafted symlink paths to access files outside the intended repository directory.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.3.22&&< 2026.4.5	2026.4.5`npm install openclaw@2026.4.5`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

≥ 2026.3.22 && < 2026.4.5

range

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.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cr8r-7g2h-6wr6 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.

Frequently Asked Questions

OpenClaw versions 2026.3.22 before 2026.4.5 contain a symlink traversal vulnerability in remote marketplace repository path handling that allows attackers to escape the expected repository root. Attackers can exploit this by providing crafted symlink paths to access files outside the intended repository directory.

O3 Security · Impact-Aware SCA

Is GHSA-cr8r-7g2h-6wr6 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

OpenClaw 2026.3.22 < 2026.4.5 - Symlink Traversal in Remote Marketplace Repository Path HandlingGHSA-cr8r-7g2h-6wr6