VulertSecurity VulertSecurity

Vulnerability Database · npm · tar · Version

tar 3.1.10

3.1.10 is affected by 18 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 7.5.22.

Critical 1 High 13 Medium 4 Low 0 Unrated 0

All tar versions & vulnerabilities → Search the database for this package →
Released 15 Aug 2017 Status deprecated release Licence BlueOak-1.0.0 Also known from other sources 0 Newer releases 153 Database updated 23/Oct/2026

Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version

tar 3.1.10 vulnerabilities

18 vulnerabilities cover tar 3.1.10. Scroll the table for all of them, or open the full list 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
CVE-2026-31802: node-tar Symlink Path Traversal Vulnerability Leading to Arbitrary File Overwrite 8.2 high 7.5.11 10 Mar 2026
Hardlink Path Traversal Vulnerability in tar Package 8.2 high 7.5.10 05 Mar 2026
CVE-2026-24842: node-tar Arbitrary File Creation/Overwrite via Hardlink Path Traversal 8.2 high 7.5.7 28 Jan 2026
Arbitrary File Overwrite and Symlink Poisoning in node-tar: A Critical Vulnerability 8.2 high 7.5.3 16 Jan 2026
CVE-2021-37701: Arbitrary File Creation/Overwrite in tar 8.2 high 4.4.16 31 Aug 2021
CVE-2021-37712: Arbitrary File Creation/Overwrite in node-tar 8.2 high 4.4.18 31 Aug 2021
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
CVE-2021-32804: Arbitrary File Creation/Overwrite in npm/tar 8.2 high 3.2.2 03 Aug 2021
CVE-2021-32803: Arbitrary File Creation/Overwrite in tar 8.2 high 3.2.3 03 Aug 2021
CVE-2026-59873: node-tar Denial of Service via Unlimited Input 7.5 critical 7.5.19 20 Jul 2026
CVE-2026-59874: node-tar Infinite Loop Vulnerability Due to Negative Tar Entry Size 7.5 high 7.5.18 20 Jul 2026
CVE-2018-20834: Arbitrary File Overwrite in tar 7.5 high 4.4.2 01 May 2019
CVE-2026-26960: Node 'tar' Package Arbitrary File Read/Write via Hardlink Target Escape 7.1 high 7.5.8 18 Feb 2026
CVE-2026-53655: Vulnerability in node-tar Allows File Smuggling via PAX Size Override 6.9 medium 7.5.16 15 Jun 2026
Uncontrolled Recursion Vulnerability in node-tar: Denial of Service Risk 5.3 medium 7.5.21 24 Jul 2026
CVE-2026-59871: node-tar Process Crash via PAX Numeric Path Type Confusion 5.3 medium 7.5.18 20 Jul 2026
CVE-2026-59875: node-tar Uncaught Exception DoS via NUL Byte in PAX Path/Linkpath Records 5.3 medium 7.5.17 20 Jul 2026

Looking for another version, or everything Vulert holds for tar?

All versions → Full vulnerability list →

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 3.1.10

Is tar 3.1.10 vulnerable?

Yes. 18 vulnerabilities in the Vulert database cover tar 3.1.10: 1 critical, 13 high, 4 medium and 0 low. The upgrade Vulert recommends is 7.5.22, and each entry above names the fixed version to move to.

Which version of tar should I use instead of 3.1.10?

7.5.22 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 3.1.10 the latest release of tar?

No. 3.1.10 was published 15 Aug 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.