Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.1amended

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

CVE-2026-53486GHSA-mp2f-45pm-3cg9

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @xhmikosr/decompress

    Affected
    < 10.2.1>= 11.0.0, < 11.1.3
    Fixed in
    11.1.3, 10.2.1

  • npm decompress

    Affected
    <= 4.2.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-53486: 0.75% estimated exploitation activity in the next 30 days; percentile 54.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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/out does 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-mp2f-45pm-3cg9

  2. Revision 2 · amended ·

    Amended from osv record GHSA-mp2f-45pm-3cg9

  3. Revision 1 · created ·

    Published from ghsa record GHSA-mp2f-45pm-3cg9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-53486

Advisory: Decompress: Archive extraction can create files and links outside of the target directory
IDs: CVE-2026-53486, GHSA-mp2f-45pm-3cg9
Record: https://patchnext.com/advisories/cve-2026-53486 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @xhmikosr/decompress 11.1.3, 10.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @xhmikosr/decompress: affected < 10.2.1; >= 11.0.0, < 11.1.3; fixed in 11.1.3, 10.2.1
- npm decompress: affected <= 4.2.1

## Suggested inspection (read-only)
- `npm ls @xhmikosr/decompress --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls decompress --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @xhmikosr/decompress, decompress.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mp2f-45pm-3cg9 (GitHub-reviewed advisory GHSA-mp2f-45pm-3cg9 lists affected ranges: npm @xhmikosr/decompress >=0 =11.0.0 =0 <=4.2.1)
- Verified: https://osv.dev/vulnerability/GHSA-mp2f-45pm-3cg9 (OSV record GHSA-mp2f-45pm-3cg9 lists affected ranges: npm @xhmikosr/decompress >=0 =11.0.0 =0 <=4.2.1)

Commands are suggestions: review each one before running it.

Loading voting…