openclaw
Affected
- introduced
2026.1.20, fixed2026.2.1(semver)
Fixed versions
2026.2.1
Fix
- Fixed version
2026.2.1npm install [email protected]
Advisory
Also known as: CVE-2026-28447
OpenClaw has a Path Traversal in Plugin Installation
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
openclaw (npm)>= 2026.1.20, < 2026.2.1>= 2026.2.12026.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):
@malicious/..unscopedPackageName("@malicious/..") yields ..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.
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.
Fix
Fixed in openclaw 2026.2.1 by validating plugin IDs and ensuring the resolved install directory remains within the configured extensions base directory.
Fix Commit(s)
Thanks @logicx24 for reporting.
High Basis: The source's own band: HIGH
2026.1.20, fixed 2026.2.1 (semver)2026.2.1
2026.2.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0