Skip to content
Fencer Intel
critical 9.1

CVE-2026-53486 json

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

published 4mo ago modified 18d ago also EUVD-2026-44465 , GHSA-mp2f-45pm-3cg9

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @xhmikosr/decompress 10.2.1, 11.1.3
  • decompress_project decompress 10.2.1, 11.1.3
  • dotnet8.0 hummingbird 1 8.0.128-1.2.hum1
  • dotnet-sdk-8.0 hummingbird 1 8.0.128-1.2.hum1
  • dotnet-hostfxr-8.0 hummingbird 1 8.0.28-1.2.hum1
  • dotnet-runtime-8.0 hummingbird 1 8.0.28-1.2.hum1
  • dotnet-sdk-dbg-8.0 hummingbird 1 8.0.128-1.2.hum1
  • dotnet-templates-8.0 hummingbird 1 8.0.128-1.2.hum1
  • aspnetcore-runtime-8.0 hummingbird 1 8.0.28-1.2.hum1
  • dotnet-runtime-dbg-8.0 hummingbird 1 8.0.28-1.2.hum1

red hat advisories RHSA-2026:40415

Is CVE-2026-53486 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-53486 updated cvss 8.1

decompress: @xhmikosr/decompress: Decompress: Arbitrary file read/write via crafted archive extraction

  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/volsync-rhel9, rhacm2/volsync-operator-bundle
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Hardened Images dotnet8.0 8.0.128-1.2.hum1, aspnetcore-runtime-8.0 8.0.28-1.2.hum1
    fixed: vendor fix RHSA-2026:40415
  • Red Hat Build of Keycloak decompress
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
3mo ago

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm @xhmikosr/decompress
<10.2.1
>=11.0.0, <11.1.3
10.2.1
11.1.3
npm decompress
<=4.2.1
 no fix listed

Affected products

  • XhmikosR decompress

Classification

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

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.