cve.bz

CVE-2026-53486 xhmikosr decompress: Path traversal

9.1 criticalEPSS 0.7%Fix available

Critical (9.1) in xhmikosr decompress. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in @xhmikosr/decompress 10.2.1, 11.1.3.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-07-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
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
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-53486 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53486?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53486?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53486 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
XhmikosR decompress< 10.2.1
XhmikosR decompress>= 11.0.0, < 11.1.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mp2f-45pm-3cg9npm@xhmikosr/decompress<10.2.110.2.1
GHSA-mp2f-45pm-3cg9npm@xhmikosr/decompress>=11.0.0 <11.1.311.1.3
GHSA-mp2f-45pm-3cg9npmdecompress<=4.2.1no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hathummingbird:1dotnet-hostfxr-8.0, dotnet-runtime-8.0, aspnetcore-runtime-8.0 and 5 more0:8.0.28-1.2.hum1RHSA-2026:40415
Red Hathummingbird:1dotnet8.0, dotnet-sdk-8.0, dotnet-sdk-dbg-8.0 and 2 more0:8.0.128-1.2.hum1RHSA-2026:40415

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Build of Keycloak, Red Hat Advanced Cluster Management (VolSync), Red Hat Hardened Images (dotnet8.0), and the Fedora/EPEL yarnpkg packages bundle the original, unmaintained npm decompress package (version 4.2.1 or earlier), which does not receive an upstream fix for this issue. None of these components use the actively maintained @xhmikosr/decompress fork that received the fix in versions 10.2.1 and 11.1.3. Red Hat rates this issue with a CVSS score of 8.1 (Important), reflecting that in these products archive extraction is performed on locally supplied or build-time archives rather than automatically on arbitrary network-supplied input, which Red Hat scores as requiring user interaction (UI:R) in contrast to the upstream CVSS score of 9.1.

Red Hat's mitigation

There is no upstream fix for the original, unmaintained decompress npm package used by these components (last release 4.2.1). The maintained fork, @xhmikosr/decompress, resolves this issue in versions 10.2.1 and 11.1.3, but is not used by any affected Red Hat component. As a general mitigation, only extract archives from trusted sources with the affected tooling, run extraction as a non-root user to prevent the setuid/setgid/sticky-bit issue from creating a privileged file, and verify that any symlinks or hardlinks produced by extraction resolve inside the intended output directory.

ProductPackageStateAdvisory
Red Hat Hardened Imagesdotnet8-0-main-8.0.128-1.2.hum1Fixed 2026-07-15RHSA-2026:40415
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/volsync-operator-bundleOut of support scope
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/volsync-rhel9Out of support scope
Red Hat Build of KeycloakdecompressNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-53486.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-732 (11).

References

Check your stackJSON