How severe is CVE-2026-32061?

No CVSS score has been assigned to CVE-2026-32061 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-32061?

CVE-2026-32061 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix CVE-2026-32061?

Update openclaw to 2026.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32061 is resolved across your whole dependency graph.

How do I detect CVE-2026-32061 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 CVE-2026-32061 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-32061 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-32061 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 CVE-2026-32061?

CVE-2026-32061 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, 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 CVE-2026-32061?

CVE-2026-32061 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 CVE-2026-32061 published, and has it been updated?

CVE-2026-32061 was published on March 11, 2026 and was last updated on October 28, 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

CVE-2026-32061 — openclaw

Fix: openclaw/openclaw@d1c00db

CVE-2026-32061 is a Path Traversal vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw < 2026.2.17 - Arbitrary File Read via $include Directive Path Traversal

Also known asGHSA-56pc-6hvp-4gv4

Published

Mar 11, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2026-32061.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk-0.03%

Lower risk than most CVEs4th percentile — riskier than 4% 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.

132other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

3.1Mdownloads / 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`npm install openclaw@2026.2.17`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.2.17

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.2.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32061 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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 CVE-2026-32061 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works