CVE-2026-53486

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

Published Jul 14, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
The decompress package for Node.js extracts archives. Prior to 10.2.1 and 11.1.3, archive extraction can create files and links outside the target directory. When extracting an archive to a directory, a crafted archive can read or write files outside that directory because hardlink and symlink entries are created without checking where targets point, path containment used a string prefix comparison, and file modes failed to remove setuid, setgid, or sticky bits. This issue is fixed in @xhmikosr/decompress versions 10.2.1 and 11.1.3.

Analysis

AI-generated

Technical impact

The decompress library extracts archives without validating that hardlink or symlink entries point inside the target directory, using a simple string prefix check. Additionally, file modes failed to remove setuid, setgid, or sticky bits, so a crafted archive can create or overwrite files anywhere on the file system where the process has permission, allowing an attacker to read or modify sensitive data or install malicious binaries.

Affected Systems

Node.js applications that depend on the XhmikosR decompress package before release v10.2.1 or v11.1.3 are affected. Any software that imports decompress for archive handling is susceptible.

Risk and Exploitability

The vulnerability has a CVSS score of 9.1, indicating high severity, but its EPSS score exploitation likelihood is low. It is not listed in the CISA KEV catalog. Exploitation requires an attacker to supply a malicious archive to the target application; if the process runs with elevated privileges, the impact is significantly higher. The attack vector is likely local or remote, depending on how the application obtains archives.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the @xhmikosr/decompress npm package to v10.2.1 or v11.1.3 or newer.
  • Restrict the archive extraction to a separate sandbox or chroot environment to limit file system impact.
  • Modify application logic to reject hardlinks and symlinks, or enforce path containment checks before extraction.

Generated by OpenCVE AI on July 31, 2026 at 05:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-mp2f-45pm-3cg9 Decompress: Archive extraction can create files and links outside of the target directory
History
Type Values Removed Values Added
First Time appeared Xhmikosr
Xhmikosr decompress
Vendors & Products Xhmikosr
Xhmikosr decompress
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The decompress package for Node.js extracts archives. Prior to 10.2.1 and 11.1.3, archive extraction can create files and links outside the target directory. When extracting an archive to a directory, a crafted archive can read or write files outside that directory because hardlink and symlink entries are created without checking where targets point, path containment used a string prefix comparison, and file modes failed to remove setuid, setgid, or sticky bits. This issue is fixed in @xhmikosr/decompress versions 10.2.1 and 11.1.3.
Title decompress: Archive extraction can create files and links outside the target directory
Weaknesses CWE-22
CWE-59
CWE-732
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-59

    Improper Link Resolution Before File Access ('Link Following')

  • CWE-732

    Incorrect Permission Assignment for Critical Resource

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 1:26 PM
Reserved
Jun 9, 2026, 5:05 PM
Status
Awaiting Analysis
Published
Jul 14, 2026, 9:17 PM
Modified
Oct 24, 2026, 9:10 PM
Severity
Important
Public date
Jul 14, 2026, 8:07 PM