CVE-2015-8860: Symlink Arbitrary File Overwrite in tar

tar Updated 02 Oct 2025

Summary

24/10/2017
Yes i
High
7.5

CVE-2015-8860: Symlink Arbitrary File Overwrite in tar. Affects tar versions < 2.0.0. Fixed in 2.0.0. How to fix ↓

Also tracked for

The same CVE-2015-8860 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The tar package is a popular utility used for archiving files and directories. It allows users to create, list, and extract files from tar archives. The vulnerability in versions prior to 2.0.0 allows for arbitrary file write attacks. When extracting symbolic links, tar fails to verify that the resolved target is within the extraction root directory.

Vulnerability Detail

The vulnerability in tar allows an attacker to create symbolic links that point to files outside of the intended extraction directory. This can lead to overwriting arbitrary files on the system, potentially allowing an attacker to modify critical files or gain unauthorized access. The vulnerability has a CVSS score of 7.5, indicating a high severity level.

How To Fix

Latest published version: 7.5.22 as of 22 Oct 2026

npm install tar@7.5.22

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.0.0

This is the first release that contains the fix.

npm install tar@2.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update to the fixed version of the tar package to mitigate the risk.

Conclusion

The tar package prior to version 2.0.0 is vulnerable to an arbitrary file write attack through symbolic links. To mitigate this vulnerability, it is crucial to update to the fixed version of the package. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for tar →

Share this vulnerability

FAQ

This vulnerability allows an attacker to overwrite arbitrary files on the system, potentially leading to unauthorized access or modification of critical files.

Versions prior to 2.0.0 are affected by this vulnerability.

You can check the version of tar by running the command 'tar --version' in your terminal.

No, there is no known workaround. It is essential to update to the fixed version of the tar package.

Related vulnerabilities

Recent vulnerabilities recorded for tar.

How To Fix

Latest published version: 7.5.22 as of 22 Oct 2026

npm install tar@7.5.22

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.0.0

This is the first release that contains the fix.

npm install tar@2.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback