Categories
CVE-2026-53486 critical CVSS 9.1

Path Traversal in @xhmikosr/decompress (CVE-2026-53486)

Summary

Path traversal in @xhmikosr/decompress (CVE-2026-53486). Confidential information can be exposed externally. Exploitable via path.relative. Mitigation: upgrade to 11.1.3 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-53486 has been found in @xhmikosr/decompress.
Attackers can target a specific entry point like path.relative over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade @xhmikosr/decompress to 11.1.3 or later.
If unsure, ask your IT team or search "@xhmikosr/decompress CVE-2026-53486" on the vendor's site.

CVE-2026-53486 (@xhmikosr/decompress) — CWE-22 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: path.relative / decompress
Patched: 11.1.3 — apply immediately
Workaround: Extract only archives you trust.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in @xhmikosr/decompress. Attackers reach the vulnerable code path via path.relative without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @xhmikosr/decompress. Attack surface: path.relative / decompress.

🔥 Severity

Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 11.1.3.

🛡️ Workaround

Workaround: Extract only archives you trust.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@xhmikosr/decompress' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r '@xhmikosr/decompress' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @xhmikosr/decompress を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    Extract only archives you trust.

    パッチが適用されるまでの応急処置として、Extract only archives you trust. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade @xhmikosr/decompress to 11.1.3

    ステージング環境で 11.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @xhmikosr/decompress
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.1.3"}]}]
npm decompress
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details