How severe is GHSA-56pc-6hvp-4gv4?

GHSA-56pc-6hvp-4gv4 has a CVSS score of 4.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-56pc-6hvp-4gv4?

GHSA-56pc-6hvp-4gv4 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-56pc-6hvp-4gv4?

Update openclaw to 2026.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56pc-6hvp-4gv4 is resolved across your whole dependency graph.

How do I detect GHSA-56pc-6hvp-4gv4 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-56pc-6hvp-4gv4 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-56pc-6hvp-4gv4?

O3 pinpoints whether GHSA-56pc-6hvp-4gv4 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-56pc-6hvp-4gv4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-56pc-6hvp-4gv4 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-56pc-6hvp-4gv4?

GHSA-56pc-6hvp-4gv4 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 4th 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-56pc-6hvp-4gv4?

GHSA-56pc-6hvp-4gv4 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-56pc-6hvp-4gv4 published, and has it been updated?

GHSA-56pc-6hvp-4gv4 was published on March 3, 2026 and was last updated on March 13, 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-56pc-6hvp-4gv4

MEDIUM

OpenClaw vulnerable to arbitrary file read via $include directive

Also known asCVE-2026-32061

Published

Mar 3, 2026

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk4th percentile+0.13%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

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

openclawnpm

4.3Mdownloads / week

Description

Vulnerability

Path traversal in config $include resolution allowed arbitrary local file reads outside the config directory boundary (CWE-22).

Attack Vectors

If an attacker can modify OpenClaw config, they can set $include to absolute paths (for example /etc/passwd) and read files accessible to the OpenClaw process.
If an attacker can modify OpenClaw config, they can use traversal paths (for example ../../...) to escape the config directory.
If an attacker can create symlinks inside the config directory, they can point includes to external files unless real-path checks are enforced.
Impact scope is bounded by the file permissions of the OpenClaw runtime user; this is not an unauthenticated remote-only vector by itself.

Impact

A successful exploit can expose local secrets and credentials readable by the OpenClaw process user, including API keys and private config material.

Affected Packages / Versions

Package: openclaw (npm)
Vulnerable versions: <=2026.2.15
Patched versions: >=2026.2.17

Fix Commit(s)

d1c00dbb7c64a39e205464dae7f2a068420e91c1

Release Process Note

Patched version is pre-set to 2026.2.17. Once npm release 2026.2.17 is available, this advisory is ready to publish.

OpenClaw thanks @aether-ai-agent for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Vulnerability Path traversal in config `$include` resolution allowed arbitrary local file reads outside the config directory boundary (CWE-22). ### Attack Vectors 1. If an attacker can modify OpenClaw config, they can set `$include` to absolute paths (for example `/etc/passwd`) and read files accessible to the OpenClaw process. 2. If an attacker can modify OpenClaw config, they can use traversal paths (for example `../../...`) to escape the config directory. 3. If an attacker can create symlinks inside the config directory, they can point includes to external files unless real-path check

O3 Security · Impact-Aware SCA

Is GHSA-56pc-6hvp-4gv4 in your dependencies?

O3 detects GHSA-56pc-6hvp-4gv4 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