Path Traversal in @xhmikosr/decompress (CVE-2026-101894)
Summary
Path traversal in @xhmikosr/decompress (CVE-2026-101894). Confidential information can be exposed externally. Exploitable via output. Mitigation: upgrade to 10.2.2 or later.
Original description
The description as published by the source.
Impact
When extracting an untrusted archive with the default decompress(input, output) API, a crafted archive containing a chain of symlink entries can make a later entry resolve outside the output directory. The lexical containment checks pass, but the kernel follows the planted symlinks to a path outside output, letting an attacker write (and read) files outside the intended extraction directory. Overwriting startup scripts or configuration can lead to remote code execution.
This is a bypass of the hardening in GHSA-mp2f-45pm-3cg9. Any application that extracts attacker-controlled archives is affected.
Patches
Fixed in 11.1.4 (latest) and backported to 10.2.2 (release-v10 dist-tag). Upgrade to one of these.
The unmaintained upstream decompress package shares this flaw and will not be patched. Migrate to @xhmikosr/decompress@11.1.4 (or @10.2.2).
Workarounds
None. Do not extract untrusted archives on affected versions. If you cannot upgrade, validate entries out of band and reject any whose resolved path escapes the target directory.
Source: NIST National Vulnerability Database 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-101894 has been found in @xhmikosr/decompress.
Attackers can target a specific entry point like output 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 10.2.2 or later.
If unsure, ask your IT team or search "@xhmikosr/decompress CVE-2026-101894" on the vendor's site.
CVE-2026-101894 (@xhmikosr/decompress) — CWE-22 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: output / latest / decompress
Patched: 10.2.2 — apply immediately
Workaround: None.
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.
Path traversal (CWE-22) exists in @xhmikosr/decompress. Attackers reach the vulnerable code path via output without authentication.
Check the vendor advisory for the affected versions of @xhmikosr/decompress. Attack surface: output / latest / decompress.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 10.2.2.
Workaround: None.
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
-
1Identify exposure identify
grep -r '@xhmikosr/decompress' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@xhmikosr/decompressを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
None.パッチが適用されるまでの応急処置として、None. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @xhmikosr/decompress to 10.2.2ステージング環境で 10.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com