# CVE-2026-53486: decompress: Archive extraction can create files and links outside the target directory

> Attackers can extract crafted archives to read or write files outside the target directory via symlink and path traversal flaws in the decompress library.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-mp2f-45pm-3cg9, MINI-3w3h-8484-5724, MINI-7qv2-q9g9-vqpc, MINI-8m6c-m56h-9vm9, MINI-cp4h-9mph-c469, MINI-f542-479x-j8q6, MINI-h8vp-3vwv-gjvg, ROOT-APP-NPM-CVE-2026-53486

## What is CVE-2026-53486?

CVE-2026-53486 is a critical path traversal vulnerability in XhmikosR decompress, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-53486?

6 open source packages ship an affected version, including @xhmikosr/decompress and decompress.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@xhmikosr/decompress` | npm | All versions | 10.2.1 |
| `@xhmikosr/decompress` | npm | All versions | 10.2.1 |
| `@xhmikosr/decompress` | npm | From 11.0.0 | 11.1.3 |
| `@xhmikosr/decompress` | npm | From 11.0.0 | 11.1.3 |
| `decompress` | npm | All versions to 4.2.1 | None |
| `decompress` | npm | All versions to 4.2.1 | None |

## How do I fix CVE-2026-53486?

Upgrade @xhmikosr/decompress to a fixed version for your release line: 10.2.1 or 11.1.3.

## Is CVE-2026-53486 being exploited?

There is no known exploitation of CVE-2026-53486 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53486 and fix it if it is affected.

What it is: CVE-2026-53486 is a critical path traversal vulnerability in XhmikosR decompress, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53486 in the wild and no public exploit code.

Affected packages and fixed versions:
- @xhmikosr/decompress (npm): affected all versions; fixed in 10.2.1
- @xhmikosr/decompress (npm): affected all versions; fixed in 10.2.1
- @xhmikosr/decompress (npm): affected from 11.0.0; fixed in 11.1.3
- @xhmikosr/decompress (npm): affected from 11.0.0; fixed in 11.1.3
- decompress (npm): affected all versions up to 4.2.1; no fix listed
- decompress (npm): affected all versions up to 4.2.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53486/ (Markdown: https://insights.sbomify.com/CVE-2026-53486/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53486
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53486
- OSV: https://osv.dev/vulnerability/CVE-2026-53486

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53486/
Summaries are generated and may contain mistakes; the official description above is the record.