Safeguard
Vulnerability Analysis•

CVE-2026-28453: OpenClaw TAR Extraction Path Traversal (Zip Slip)

CVE-2026-28453 lets a crafted TAR archive write files outside the extraction directory in OpenClaw plugin and hook installs. Upgrade to 2026.2.14.

Safeguard Security Team
3 min read

CVE-2026-28453 is a path traversal flaw, known as Zip Slip, in how OpenClaw extracts TAR archives. A crafted archive can write files outside the intended directory, which can lead to configuration tampering and code execution. NVD scores it 7.5. Upgrade openclaw to 2026.2.14.

What's affected

The GitHub advisory GHSA-p25h-9q54-ffvw lists affected versions before 2026.2.14 and patched versions 2026.2.14 and later of the npm package openclaw.

The affected code is the archive extraction function used by installation flows, including installing plugins and installing hooks. The advisory says the issue arises if a user installs an untrusted TAR or tgz archive. It needs the user to act, which is why the advisory's vector shows user interaction required.

The advisory rates it High at 8.1, and NVD shows 7.5. The weakness is CWE-22 (Path Traversal). Files are written within the permissions of the OpenClaw process.

How to check if you're exposed

Check the OpenClaw version in each project and global install.

npm ls openclaw
npm ls -g openclaw

Then review how your team installs plugins and hooks. Where do the archives come from? Archives from an official source you verified are different from archives from a chat message, a forum or an unknown repository.

What to do now

  1. Upgrade openclaw to 2026.2.14 or later.
  2. Do not install plugin or hook archives from sources you have not verified.
  3. Run OpenClaw as a low privileged user with write access limited to its own directories.
  4. Review the configuration and hooks directories for files you did not create, if you installed archives from unverified sources.
  5. Add archive installation to your change review process.

Why it matters

Archives store each file with a path. A malicious archive can include entries whose paths climb out of the destination folder with parent directory references, or use absolute paths. If the extractor writes them as given, the archive controls where files land.

The advisory says extraction used a library call with only a working directory set and did not reject traversal or absolute entries. The fix is to validate every entry path before writing. The safe rule is that each resolved path must remain inside the destination.

Writing outside the folder matters because configuration and plugin directories control what the application loads. Tampering with them can lead to code execution, which is what the advisory warns about.

The record does not flag exploitation in the wild, and the CVE is not in CISA's Known Exploited Vulnerabilities catalog. A pull request gate that checks changes to dependencies and install scripts is a useful control, as the demo below shows.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Do I need to install a malicious archive for this to matter?

Yes. The advisory says the risk arises when a user installs an untrusted archive. Verify sources before installing.

What is Zip Slip?

A class of bug where archive entries use traversal sequences to write files outside the extraction directory. It also affects ZIP files and other formats.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.