VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

tar: vulnerability history, versions and safety

tar is a package in the npm ecosystem. Vulert records 21 vulnerabilities for it across 118 releases, from Oct 2017 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded C1 H14 M6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
14 in the last 12 months

Most recent disclosure 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tar vulnerabilities

Vulert verdict on tar 7.5.22 i

Updated on 22 Oct 2026

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

Package health score 63/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 7.5.22 — unaffected i
  • Vulnerabilities on record 21 over 8 years · 14 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 23,574 packages i
  • Stars 923 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence BlueOak-1.0.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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, 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
7.5.22 24 Jul 2026 none BlueOak-1.0.0 — Details →
7.5.21 21 Jul 2026 none BlueOak-1.0.0 — Details →
7.5.20 12 Jul 2026 M1 BlueOak-1.0.0 Yes Details →
7.5.19 27 Jun 2026 M1 BlueOak-1.0.0 Yes Details →
7.5.18 27 Jun 2026 C1 M1 BlueOak-1.0.0 Yes Details →
7.5.17 25 Jun 2026 C1 H1 M2 BlueOak-1.0.0 Yes Details →
7.5.16 01 Jun 2026 C1 H1 M3 BlueOak-1.0.0 Yes Details →
7.5.15 07 May 2026 C1 H1 M4 BlueOak-1.0.0 Yes Details →
7.5.14 05 May 2026 C1 H1 M4 BlueOak-1.0.0 Yes Details →
7.5.13 23 Mar 2026 C1 H1 M4 BlueOak-1.0.0 Yes Details →
7.5.12 20 Mar 2026 C1 H1 M4 BlueOak-1.0.0 Yes Details →
7.5.11 09 Mar 2026 C1 H1 M4 BlueOak-1.0.0 Yes Details →
7.5.10 04 Mar 2026 C1 H2 M4 BlueOak-1.0.0 Yes Details →
7.5.9 16 Feb 2026 C1 H3 M4 BlueOak-1.0.0 Yes Details →
7.5.8 16 Feb 2026 C1 H3 M4 BlueOak-1.0.0 Yes Details →
7.5.7 27 Jan 2026 C1 H4 M4 BlueOak-1.0.0 Yes Details →
7.5.6 21 Jan 2026 C1 H5 M4 BlueOak-1.0.0 Yes Details →
7.5.5 20 Jan 2026 C1 H5 M4 BlueOak-1.0.0 Yes Details →
7.5.4 19 Jan 2026 C1 H5 M4 BlueOak-1.0.0 Yes Details →
7.5.3 16 Jan 2026 C1 H6 M4 BlueOak-1.0.0 Yes Details →
7.5.2 30 Oct 2025 C1 H7 M4 BlueOak-1.0.0 Yes Details →
7.5.1 23 Sep 2025 M2 ISC Yes Details →
7.5.0 23 Sep 2025 C1 H7 M4 ISC Yes Details →
7.4.4 22 Sep 2025 C1 H7 M4 ISC Yes Details →
7.4.3 26 Jul 2024 C1 H7 M4 ISC Yes Details →
7.4.2 24 Jul 2024 C1 H7 M4 ISC Yes Details →
7.4.1 22 Jul 2024 C1 H7 M4 ISC Yes Details →
7.4.0 19 Jun 2024 C1 H7 M4 ISC Yes Details →
7.3.0 19 Jun 2024 C1 H7 M4 ISC Yes Details →
7.2.0 30 May 2024 C1 H7 M4 ISC Yes Details →
7.1.0 04 May 2024 C1 H7 M4 ISC Yes Details →
7.0.1 14 Apr 2024 C1 H7 M4 ISC Yes Details →
7.0.0 10 Apr 2024 C1 H7 M4 ISC Yes Details →
6.2.1 21 Mar 2024 C1 H7 M4 ISC Yes Details →
6.2.0 05 Sep 2023 C1 H7 M4 ISC Yes Details →
6.1.15 17 May 2023 C1 H7 M4 ISC Yes Details →
6.1.14 02 May 2023 C1 H7 M4 ISC Yes Details →
6.1.13 07 Dec 2022 C1 H7 M4 ISC Yes Details →
6.1.12 01 Nov 2022 C1 H7 M4 ISC Yes Details →
6.1.11 26 Aug 2021 C1 H7 M4 ISC Yes Details →
4.4.19 19 Aug 2021 C1 H7 M4 ISC Yes Details →
5.0.11 19 Aug 2021 C1 H7 M4 ISC Yes Details →
6.1.10 19 Aug 2021 C1 H7 M4 ISC Yes Details →
4.4.18 19 Aug 2021 C1 H7 M4 ISC Yes Details →
5.0.10 19 Aug 2021 C1 H7 M4 ISC Yes Details →
6.1.9 19 Aug 2021 C1 H7 M4 ISC Yes Details →
5.0.9 11 Aug 2021 C1 H7 M4 ISC Yes Details →
4.4.17 11 Aug 2021 C1 H9 M4 ISC Yes Details →
6.1.8 11 Aug 2021 C1 H7 M4 ISC Yes Details →
4.4.16 09 Aug 2021 C1 H9 M4 ISC Yes Details →
5.0.8 09 Aug 2021 C1 H7 M4 ISC Yes Details →
6.1.7 09 Aug 2021 C1 H7 M4 ISC Yes Details →
6.1.6 04 Aug 2021 C1 H7 M4 ISC Yes Details →
6.1.5 04 Aug 2021 C1 H7 M4 ISC Yes Details →
6.1.4 03 Aug 2021 C1 H7 M4 ISC Yes Details →
6.1.3 02 Aug 2021 C1 H7 M4 ISC Yes Details →
3.2.3 26 Jul 2021 C1 H11 M4 ISC Yes Details →
4.4.15 26 Jul 2021 C1 H10 M4 ISC Yes Details →
5.0.7 26 Jul 2021 C1 H7 M4 ISC Yes Details →
6.1.2 26 Jul 2021 C1 H7 M4 ISC Yes Details →
6.1.1 23 Jul 2021 C1 H7 M4 ISC Yes Details →
3.2.2 23 Jul 2021 C1 H12 M4 ISC Yes Details →
4.4.14 23 Jul 2021 C1 H10 M4 ISC Yes Details →
5.0.6 23 Jul 2021 C1 H7 M4 ISC Yes Details →
6.1.0 07 Jan 2021 C1 H7 M4 ISC Yes Details →
6.0.5 14 Aug 2020 C1 H7 M4 ISC Yes Details →
6.0.4 14 Aug 2020 C1 H7 M4 ISC Yes Details →
6.0.3 14 Aug 2020 C1 H7 M4 ISC Yes Details →
6.0.2 27 Apr 2020 C1 H7 M4 ISC Yes Details →
6.0.1 29 Jan 2020 C1 H7 M4 ISC Yes Details →
6.0.0 28 Jan 2020 C1 H7 M4 ISC Yes Details →
5.0.5 05 Oct 2019 C1 H7 M4 ISC Yes Details →
5.0.4 05 Oct 2019 C1 H7 M4 ISC Yes Details →
5.0.2 30 Sep 2019 C1 H7 M4 ISC Yes Details →
5.0.1 26 Sep 2019 C1 H7 M4 ISC Yes Details →
5.0.0 25 Sep 2019 C1 H7 M4 ISC Yes Details →
4.4.13 25 Sep 2019 C1 H10 M4 ISC Yes Details →
4.4.12 24 Sep 2019 C1 H10 M4 ISC Yes Details →
4.4.11 17 Sep 2019 C1 H10 M4 ISC Yes Details →
4.4.10 04 Jun 2019 C1 H10 M4 ISC Yes Details →
4.4.9 01 Jun 2019 C1 H10 M4 ISC Yes Details →
2.2.2 15 May 2019 C1 H9 M4 ISC Yes Details →
4.4.8 08 Nov 2018 C1 H10 M4 ISC Yes Details →
4.4.7 05 Nov 2018 C1 H10 M4 ISC Yes Details →
4.4.6 02 Aug 2018 C1 H10 M4 ISC Yes Details →
4.4.5 02 Aug 2018 C1 H10 M4 ISC Yes Details →
4.4.4 25 May 2018 C1 H10 M4 ISC Yes Details →
4.4.3 23 May 2018 C1 H10 M4 ISC Yes Details →
4.4.2 30 Apr 2018 C1 H10 M4 ISC Yes Details →
4.4.1 20 Mar 2018 C1 H11 M4 ISC Yes Details →
4.4.0 20 Feb 2018 C1 H11 M4 ISC Yes Details →
4.3.3 06 Feb 2018 C1 H11 M4 ISC Yes Details →
4.3.2 01 Feb 2018 C1 H11 M4 ISC Yes Details →
4.3.1 01 Feb 2018 C1 H11 M4 ISC Yes Details →
4.3.0 18 Jan 2018 C1 H11 M4 ISC Yes Details →
4.2.0 21 Dec 2017 C1 H11 M4 ISC Yes Details →
4.1.2 21 Dec 2017 C1 H11 M4 ISC Yes Details →
4.1.1 28 Nov 2017 C1 H11 M4 ISC Yes Details →
4.1.0 28 Nov 2017 C1 H11 M4 ISC Yes Details →
4.0.2 18 Oct 2017 C1 H11 M4 ISC Yes Details →
3.2.1 21 Aug 2017 C1 H13 M4 — Yes Details →
4.0.1 21 Aug 2017 C1 H11 M4 — Yes Details →
4.0.0 18 Aug 2017 C1 H11 M4 — Yes Details →
3.2.0 17 Aug 2017 C1 H13 M4 — Yes Details →
3.1.15 17 Aug 2017 C1 H13 M4 — Yes Details →
3.1.14 16 Aug 2017 C1 H13 M4 — Yes Details →
3.1.13 16 Aug 2017 C1 H13 M4 — Yes Details →
3.1.12 15 Aug 2017 C1 H13 M4 — Yes Details →
3.1.11 15 Aug 2017 C1 H13 M4 — Yes Details →
3.1.10 15 Aug 2017 C1 H13 M4 — Yes Details →
3.1.9 02 Aug 2017 C1 H13 M4 — Yes Details →
3.1.8 01 Aug 2017 C1 H13 M4 — Yes Details →
3.1.7 26 Jul 2017 C1 H13 M4 — Yes Details →
3.1.6 25 Jul 2017 C1 H13 M4 — Yes Details →
3.1.5 03 Jun 2017 C1 H13 M4 — Yes Details →
3.1.4 02 Jun 2017 C1 H13 M4 — Yes Details →
3.1.3 16 May 2017 C1 H13 M4 — Yes Details →
3.1.2 12 May 2017 C1 H13 M4 — Yes Details →
3.1.1 12 May 2017 C1 H13 M4 — Yes Details →
3.1.0 12 May 2017 C1 H13 M4 — Yes Details →

The newest 120 of 153 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2019 1
  • 2021 5
  • 2025 2
  • 2026 12

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

03 Vulnerabilities

Recorded vulnerabilities for tar

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-23950: Race Condition in node-tar Allows Symlink Poisoning on macOS APFS 8.8 high 7.5.4 21 Jan 2026
Hardlink Path Traversal Vulnerability in tar Package 8.2 high 7.5.10 05 Mar 2026
CVE-2021-37713: Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization in tar 8.2 high 4.4.18 31 Aug 2021
Arbitrary File Overwrite and Symlink Poisoning in node-tar: A Critical Vulnerability 8.2 high 7.5.3 16 Jan 2026
CVE-2021-37712: Arbitrary File Creation/Overwrite in node-tar 8.2 high 4.4.18 31 Aug 2021

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524167

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About tar

Is tar safe to use?

Vulert records 21 vulnerabilities for tar in npm: 1 critical, 14 high, 6 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's Vulert package health score?

Vulert scores tar 63/100, which reads as usable, but worth attention. 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 affected?

No. 7.5.22, 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 should I use?

7.5.22 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 have?

21 vulnerabilities are recorded for tar in the npm ecosystem: 1 critical, 14 high, 6 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 vulnerabilities disclosed?

14 vulnerabilities were recorded for tar in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 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 for upcoming vulnerabilities?

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