Intel

AIKIDO-2026-557740

@zip.js/zip.js is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Pre-CVE
Found by Aikido Intel before public disclosure or CVE publication.
Published Oct 20, 2026
October 20, 2026

50

CVE Score

Medium

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Are you affected? Scan for Free

TL;DR

ZipReader.getEntries() and getEntriesGenerator() in lib/core/zip-reader.js pass each archive entry filename to isUnsafeFilename() when filenameValidation, or its fallback strictness, is set to "balanced" or "strict", the library's documented default. That check rejects a ".." path component only when slashes separate it, and it rejects a filename that starts with two backslashes, so a backslash delimited ".." segment such as ..\file.txt is accepted and Windows resolves it as a parent directory traversal. The fix makes isUnsafeFilename() reject backslash delimited ".." segments.

How do I fix this?

Upgrade the @zip.js/zip.js library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you extract an untrusted ZIP archive on Windows using archive supplied filenames.

Versions

2.8.50 - 2.14.1

Fixed in 2.15.0

Background info

@zip.js/zip.js is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in versions 2.8.50 - 2.14.1.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea