Packages / tar-fs / Security

HighVulnerabilityGHSA-vj76-c3g6-qr5vCVE-2025-59343Published 24 Sep 2025

tar-fs has a symlink validation bypass if destination directory is predictable with a specific tarball

Your version

Affected releases · tar-fs

  • 3.x3.0.0 – 3.1.0Fixed in 3.1.1
  • 2.x2.0.0 – 2.1.3Fixed in 2.1.4
  • 1.x1.0.0 – 1.16.5Fixed in 1.16.6
  • 0.5.x and older0.1.0 – 0.5.2No fix, no longer updated

On 3.x, the newest line:

npm install tar-fs@3.1.1
Every release on a timeline
3.x
  1. Affected

    3.0.0 – 3.1.0

    12 releases

  2. Fixed

    3.1.1 – 3.1.3

    3 releases, latest

2.x
  1. Affected

    2.0.0 – 2.1.3

    6 releases

  2. Fixed

    2.1.4 – 2.1.5

    2 releases

1.x
  1. Affected

    1.0.0 – 1.16.5

    32 releases

  2. Fixed

    1.16.6

    1 release

0.x
  1. Affected

    0.1.0 – 0.5.2

    21 releases

77 stable releases of tar-fs, oldest to newest, one row per major.

What happens

Impact

v3.1.0, v2.1.3, v1.16.5 and below

Patches

Has been patched in 3.1.1, 2.1.4, and 1.16.6

Workarounds

You can use the ignore option to ignore non files/directories.

  ignore (_, header) {
    // pass files & directories, ignore e.g. symlinks
    return header.type !== 'file' && header.type !== 'directory'
  }

Credit

Reported by: Mapta / BugBunny_ai

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.