tar

7.5.22 · 24 Jul 2026BlueOak-1.0.0117.9M / weekRepository Homepage npm Atom feed

Upgrading tar From 5.0.9 to 5.0.11

Same major only

2 releases in betweennotes for 0

Other targets from 5.0.9Clears its 15 advisories7.5.21 Latest7.5.22

5.0.9yours
5.0.10
5.0.11target

?
changes to make: 2
advisories fixed: ?
new: ?
fixes

Counted from 0 of 2 release notes. Advisories are counted from the advisory database, in full.

Security

13 advisories still affect 5.0.11

node-tar: Decompression/parse DoS via unlimited inputcritical · GHSA-23hp-3jrh-7fpw
node-tar Vulnerable to Arbitrary File Creation/Overwrite via Hardlink Path Traversalhigh · GHSA-34x7-hfp2-rc4v
Arbitrary File Read/Write via Hardlink Target Escape Through Symlink Chain in node-tar Extractionhigh · GHSA-83g3-92jg-28cx

Upgrading to 7.5.21 clears them.

Fixes 2 advisories affecting 5.0.9

Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitizationhigh · GHSA-5955-9wpr-37jh
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic linkshigh · GHSA-qq89-hq3f-393p

Upgrade to 5.0.11

npm install tar@5.0.11

What 5.0.11 needs

Reading 5.0.11's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 5.0.11. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
13 advisories still affect 5.0.11.