GHSA-mp2f-45pm-3cg9
Suggest an improvement- Source
- https://github.com/advisories/GHSA-mp2f-45pm-3cg9
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/07/GHSA-mp2f-45pm-3cg9/GHSA-mp2f-45pm-3cg9.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-mp2f-45pm-3cg9
- Aliases
-
- CVE-2026-53486
- Published
- 2026-07-06T20:27:38Z
- Modified
- 2026-07-06T20:45:10.040835853Z
- Severity
-
- 9.1 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CVSS Calculator
- Summary
- Decompress: Archive extraction can create files and links outside of the target directory
- Details
-
Impact
When extracting an archive to a directory, a crafted archive can read or write files outside that directory. The flaw is in the code that writes the parsed entries, so it affects every format decompress handles: tar, tar.gz, tar.bz2, and zip by default, plus any others added through the plugins option.
A link (hardlink) or symlink entry is created without checking where its target points. A hardlink can be aimed at any file the running process can read; that file then appears inside the output directory and its contents are exposed. A symlink can point outside the output directory and redirect a later write.
The path containment check used a string prefix comparison (
realPath.indexOf(outputPath) !== 0). Output/srv/outdoes not contain/srv/out-old, but the prefix comparison treats it as inside, so an entry can escape into a sibling directory whose name starts with the output directory name.File modes were applied as
mode & ~umask, which does not remove the setuid, setgid, or sticky bits. A crafted entry can create a setuid or setgid file. This matters when extraction runs as root, for example in CI, containers, or install scripts.Any code that extracts archives from an untrusted or attacker-influenced source is affected. Archives are commonly downloaded before extraction, so this is reachable over the network in many setups.
Patches
Fixed in
@xhmikosr/decompress10.2.1 and 11.1.3. Link targets are now resolved and checked against the output directory, containment usespath.relative, and setuid, setgid, and sticky bits are removed.The upstream
decompresspackage is unmaintained, and all versions through its last release (4.2.1) have the same flaws. There is no upstream fix. Migrate to@xhmikosr/decompress11.1.3 or later.Workarounds
Extract only archives you trust. Run extraction as a non-root user so the mode issue cannot create a privileged file. After extracting, reject any symlink or hardlink that points outside the target and any file with unexpected mode bits.
Resources
- Related prior issue in the upstream project this package forks: CVE-2020-12265 / GHSA-qgfr-5hqp-vrw9
- Fix commits and releases:
- https://github.com/XhmikosR/decompress/releases/tag/v10.2.1
- https://github.com/XhmikosR/decompress/releases/tag/v11.1.3
- https://github.com/XhmikosR/decompress/commit/aca5aac
- https://github.com/XhmikosR/decompress/commit/281cefa
- https://github.com/XhmikosR/decompress/commit/60b5299
- Database specific
{ "github_reviewed_at": "2026-07-06T20:27:38Z", "cwe_ids": [ "CWE-22", "CWE-59", "CWE-732" ], "github_reviewed": true, "nvd_published_at": null, "severity": "CRITICAL" }- References
Affected packages
npm / @xhmikosr/decompress
Package
- Name
- @xhmikosr/decompress
- View open source insights on deps.dev
- Purl
- pkg:npm/%40xhmikosr%2Fdecompress
npm / @xhmikosr/decompress
Package
- Name
- @xhmikosr/decompress
- View open source insights on deps.dev
- Purl
- pkg:npm/%40xhmikosr%2Fdecompress
npm / decompress
Package
- Name
- decompress
- View open source insights on deps.dev
- Purl
- pkg:npm/decompress