CVE-2026-32061

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 checks are enforced.
4. Impact scope is bounded by the file permissions of the OpenClaw runtime user; this is not an unauthenticated remote-only vector by itself.

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.

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

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-32061 has a CVSS score of 4.4 (Medium). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.17); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32061? CVE-2026-32061 is a medium-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.17. It is fixed in 2026.2.17. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-32061? CVE-2026-32061 has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32061? openclaw (npm) versions < 2026.2.17 is affected.
4. Is there a fix for CVE-2026-32061? Yes. CVE-2026-32061 is fixed in 2026.2.17. Upgrade to this version or later.
5. Is CVE-2026-32061 exploitable, and should I be worried? Whether CVE-2026-32061 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32061 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32061? Upgrade openclaw to 2026.2.17 or later.