Is decompress 4.1 vulnerable?

npm · 1 release from 4.1.0 to 4.1.0 · latest decompress is 4.2.1 · checked 1 Nov 2026

Yes: 5 known advisories

Yes. decompress 4.1.0, the last 4.1 release, is affected by 5 known security advisories (3 critical, 2 medium), including CVE-2026-101894, CVE-2026-53486, CVE-2020-12265. At least one has no fixed release yet.

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting decompress 4.1.0

  • CriticalCVE-2026-101894GHSA-hrh2-vp3x-79xf29 Sept 2026

    @xhmikosr/decompress: Path traversal via symlink chain

    Affected
    <=4.2.1
    Fixed in
    No fix released
  • MediumCVE-2026-39243GHSA-jwp9-9v96-94mx10 Jul 2026

    decompress allows arbitrary hardlink creation during archive extraction

    Affected
    <=4.2.1
    Fixed in
    No fix released
  • CriticalCVE-2026-53486GHSA-mp2f-45pm-3cg96 Jul 2026

    Decompress: Archive extraction can create files and links outside of the target directory

    Affected
    <=4.2.1
    Fixed in
    No fix released
  • MediumCVE-2026-10732GHSA-h39j-r5qq-r9mm5 Jun 2026

    decompress: Arbitrary File Write via Archive Extraction (Zip Slip)

    Affected
    <=4.2.1
    Fixed in
    No fix released
  • CriticalCVE-2020-12265GHSA-qgfr-5hqp-vrw93 Sept 2020

    Path Traversal in decompress

    Affected
    <4.2.1
    Fixed in
    4.2.1

Which of your client projects are still on decompress 4.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact decompress version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other decompress versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.