Summary
OpenClaw's plugin installation path derivation could be abused by a malicious plugin package.json name to escape the intended extensions directory and write files to a parent directory.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
>= 2026.1.20, < 2026.2.1 - Fixed:
>= 2026.2.1 - Latest published as of 2026-02-14:
2026.2.13(not affected)
Details
In affected versions, the plugin installer derives the on-disk install directory from the plugin manifest name without robust validation.
Example (POSIX / macOS / Linux):
- Manifest name:
@malicious/.. unscopedPackageName("@malicious/..")yields..- The install directory becomes
path.join(extensionsDir, ".."), which resolves to the parent of the extensions directory.
This can cause plugin files to be written into the OpenClaw state directory (default ~/.openclaw/) rather than a subdirectory of ~/.openclaw/extensions/.
Note: on Windows, affected versions also failed to sanitize backslashes (\\) in the derived directory name, which can enable deeper traversal via crafted pluginId strings.
Fix Commit(s)
- d03eca8450dc493b198a88b105fd180895238e57
Thanks @logicx24 for reporting.
Impact
This issue requires a user/operator to install untrusted plugin content (for example via openclaw plugins install). In many deployments, plugin installation is an operator-only action and may be performed on a separate machine; that operational separation significantly reduces exposure for the primary gateway/runtime host.
On hosts where untrusted plugins are installed, this can lead to unintended file writes outside the extensions directory (potentially overwriting files under the OpenClaw state directory). On Windows, the traversal surface may extend further, within the privileges of the user running OpenClaw.
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-28447 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and user interaction required. 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.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Fixed in openclaw 2026.2.1 by validating plugin IDs and ensuring the resolved install directory remains within the configured extensions base directory.
Frequently Asked Questions
- What is CVE-2026-28447? CVE-2026-28447 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions >= 2026.1.20, < 2026.2.1. It is fixed in 2026.2.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is CVE-2026-28447? CVE-2026-28447 has a CVSS score of 8.1 (High). 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.
- Which versions of openclaw are affected by CVE-2026-28447? openclaw (npm) versions >= 2026.1.20, < 2026.2.1 is affected.
- Is there a fix for CVE-2026-28447? Yes. CVE-2026-28447 is fixed in 2026.2.1. Upgrade to this version or later.
- Is CVE-2026-28447 exploitable, and should I be worried? Whether CVE-2026-28447 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
- What actually determines whether CVE-2026-28447 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.
- How do I fix CVE-2026-28447? Upgrade
openclawto 2026.2.1 or later.