VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

tar-fs: vulnerability history, versions and safety

tar-fs is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 64 releases, from May 2019 to Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tar-fs vulnerabilities

Vulert verdict on tar-fs 3.1.3 i

Updated on 23 Oct 2026

Good news: 3.1.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 3.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.1.3 — unaffected i
  • Vulnerabilities on record 4 over 6 years · 0 in the last year i
  • Latest disclosure 24 Sep 2025 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Depended on by 13,758 packages i
  • Stars 383 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for tar-fs, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.1.3 27 Jun 2026 none MIT — Details →
2.1.5 27 Jun 2026 none MIT — Details →
3.1.2 04 Mar 2026 none MIT — Details →
1.16.6 16 Sep 2025 none MIT — Details →
2.1.4 16 Sep 2025 none MIT — Details →
3.1.1 16 Sep 2025 none MIT — Details →
3.1.0 30 Jun 2025 H1 MIT Yes Details →
3.0.10 16 Jun 2025 H1 MIT Yes Details →
1.16.5 22 May 2025 none MIT — Details →
2.1.3 22 May 2025 none MIT — Details →
3.0.9 22 May 2025 H1 MIT Yes Details →
3.0.8 14 Jan 2025 H1 MIT Yes Details →
1.16.4 12 Jan 2025 H1 MIT Yes Details →
2.1.2 12 Jan 2025 none MIT — Details →
3.0.7 12 Jan 2025 H1 MIT Yes Details →
3.0.6 26 Apr 2024 H1 MIT Yes Details →
3.0.5 09 Feb 2024 H1 MIT Yes Details →
3.0.4 02 Jul 2023 H1 MIT Yes Details →
3.0.3 20 Jun 2023 H1 MIT Yes Details →
3.0.2 17 Jun 2023 H1 MIT Yes Details →
3.0.1 17 Jun 2023 H1 MIT Yes Details →
3.0.0 17 Jun 2023 H1 MIT Yes Details →
2.1.1 06 Nov 2020 none MIT — Details →
2.1.0 11 May 2020 none MIT — Details →
2.0.1 24 Mar 2020 none MIT — Details →
2.0.0 04 Feb 2019 none MIT — Details →
1.16.3 20 Jun 2018 H2 MIT Yes Details →
1.16.2 30 Apr 2018 H2 MIT Yes Details →
1.16.1 29 Apr 2018 H3 MIT Yes Details →
1.16.0 05 Oct 2017 H3 MIT Yes Details →
1.15.3 06 Jun 2017 H3 MIT Yes Details →
1.15.2 21 Mar 2017 H3 MIT Yes Details →
1.15.1 22 Feb 2017 H3 MIT Yes Details →
1.15.0 16 Dec 2016 H3 MIT Yes Details →
1.14.0 12 Oct 2016 H3 MIT Yes Details →
1.13.2 21 Aug 2016 H3 MIT Yes Details →
1.13.1 18 Aug 2016 H3 MIT Yes Details →
1.13.0 22 May 2016 H3 MIT Yes Details →
1.12.0 31 Mar 2016 H3 MIT Yes Details →
1.11.1 28 Feb 2016 H3 MIT Yes Details →
1.11.0 27 Feb 2016 H3 MIT Yes Details →
1.10.0 09 Feb 2016 H3 MIT Yes Details →
1.9.0 16 Dec 2015 H3 MIT Yes Details →
1.8.1 30 Jul 2015 H3 MIT Yes Details →
1.8.0 28 Jul 2015 H3 MIT Yes Details →
1.7.0 30 Jun 2015 H3 MIT Yes Details →
1.6.0 22 Jun 2015 H3 MIT Yes Details →
1.5.1 14 May 2015 H3 MIT Yes Details →
1.5.0 02 Mar 2015 H3 MIT Yes Details →
1.4.2 07 Jan 2015 H3 MIT Yes Details →
1.4.1 04 Dec 2014 H3 MIT Yes Details →
1.4.0 27 Nov 2014 H3 MIT Yes Details →
1.3.0 25 Nov 2014 H3 MIT Yes Details →
1.2.0 16 Oct 2014 H3 MIT Yes Details →
1.1.0 10 Oct 2014 H3 MIT Yes Details →
1.0.0 24 Sep 2014 H3 MIT Yes Details →
0.5.2 23 Sep 2014 H3 MIT Yes Details →
0.5.1 23 Sep 2014 H3 MIT Yes Details →
0.5.0 20 Aug 2014 H3 MIT Yes Details →
0.4.1 10 Jul 2014 H3 MIT Yes Details →
0.4.0 10 Jul 2014 H3 MIT Yes Details →
0.3.3 30 May 2014 H3 MIT Yes Details →
0.3.2 11 Apr 2014 H3 MIT Yes Details →
0.3.1 03 Apr 2014 H3 MIT Yes Details →
0.3.0 31 Mar 2014 H3 MIT Yes Details →
0.2.2 12 Feb 2014 H3 MIT Yes Details →
0.2.1 12 Feb 2014 H3 MIT Yes Details →
0.2.0 12 Feb 2014 H3 MIT Yes Details →
0.1.8 28 Jan 2014 H3 MIT Yes Details →
0.1.7 13 Jan 2014 H3 MIT Yes Details →
0.1.6 25 Dec 2013 H3 MIT Yes Details →
0.1.5 23 Dec 2013 H3 MIT Yes Details →
0.1.4 23 Dec 2013 H3 MIT Yes Details →
0.1.3 23 Dec 2013 H3 MIT Yes Details →
0.1.2 23 Dec 2013 H3 MIT Yes Details →
0.1.1 21 Dec 2013 H3 MIT Yes Details →
0.1.0 21 Dec 2013 H3 MIT Yes Details →

All 77 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2025 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for tar-fs

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-48387: tar-fs Package Vulnerability Allowing Extraction Outside Specified Directory 8.7 high 1.16.5 03 Jun 2025
Symlink Validation Bypass in tar-fs Package 8.7 high 3.1.1 24 Sep 2025
CVE-2018-20835: Improper Input Validation in tar-fs 7.5 high 1.16.2 01 May 2019
High Severity Path Traversal Vulnerability in tar-fs Package 7.5 high 1.16.4 27 Mar 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About tar-fs

Is tar-fs safe to use?

Vulert records 4 vulnerabilities for tar-fs in npm: 0 critical, 4 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is tar-fs's Vulert package health score?

Vulert scores tar-fs 77/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of tar-fs affected?

No. 3.1.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of tar-fs should I use?

3.1.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does tar-fs have?

4 vulnerabilities are recorded for tar-fs in the npm ecosystem: 0 critical, 4 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tar-fs vulnerabilities disclosed?

0 vulnerabilities were recorded for tar-fs in the last 12 months, and the oldest entry in this database dates to 01 May 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of tar-fs are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor tar-fs for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tar-fs version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.