CVE-2026-28453

OpenClaw versions before 2026.2.14 did not sufficiently validate TAR archive entry paths during extraction. A crafted archive could use path traversal sequences (for example ../../...) to write files outside the intended destination directory (Zip Slip).

Affected Packages / Versions

• Package: openclaw (npm)
• Affected: < 2026.2.14
• Fixed: >= 2026.2.14

Details

The affected code path is extractArchive() in src/infra/archive.ts. Prior to 2026.2.14, TAR extraction used tar.x({ cwd: destDir }) without rejecting traversal and absolute entry paths.

This extraction is used by installation flows such as:

• openclaw plugins install …
• openclaw hooks install …

Mitigation

Upgrade to openclaw >= 2026.2.14. Avoid installing untrusted plugin/hook archives.

Fix Commit(s)

• 3aa94afcfd12104c683c9cad81faf434d0dadf87

OpenClaw thanks @xuemian168 for reporting.

If a user installs an untrusted .tar / .tgz archive, an attacker can write files outside the extraction directory (within the permissions of the OpenClaw process). This can lead to configuration tampering and potentially code execution.

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-28453 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.14); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-28453? CVE-2026-28453 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.14. It is fixed in 2026.2.14. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-28453? CVE-2026-28453 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.
3. Which versions of openclaw are affected by CVE-2026-28453? openclaw (npm) versions < 2026.2.14 is affected.
4. Is there a fix for CVE-2026-28453? Yes. CVE-2026-28453 is fixed in 2026.2.14. Upgrade to this version or later.
5. Is CVE-2026-28453 exploitable, and should I be worried? Whether CVE-2026-28453 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-28453 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-28453? Upgrade openclaw to 2026.2.14 or later.