Is CVE-2026-101894 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-101894 being exploited in the wild.

How severe is CVE-2026-101894?

Critical severity, with a CVSS score of 9.1, published 28 September 2026.

Which products and versions are affected?

Kevva Decompress through 4.2.1 (unmaintained); @xhmikosr/decompress (npm) SEMVER:introduced=11.0.0,fixed=11.1.4; decompress (npm) SEMVER:introduced=0,last_affected=4.2.1; XhmikosR Decompress before 10.2.2 and 11.1.4.

Is there a fix for CVE-2026-101894?

Yes. @xhmikosr/decompress (npm): upgrade to 11.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-101894 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-101894?

Check whether you run Kevva Decompress, @xhmikosr/decompress (npm), decompress (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-101894: decompress package path traversal via symlink chains

CVE-2026-101894 · Severity: critical · CVSS 9.1 · Published 2026-09-28

The decompress package for Node.js extracts archive files to a specified directory. A flaw in its symlink validation logic allows attackers to supply specially crafted archives containing chained symlinks that escape the intended output directory, enabling arbitrary file read/write and potentially remote code execution through overwriting startup scripts or configuration files.

Technologies: decompress (npm). Vendors: npm.

Quick answers

Is CVE-2026-101894 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101894 being exploited in the wild.
How severe is CVE-2026-101894?: Critical severity, with a CVSS score of 9.1, published 28 September 2026.
Which products and versions are affected?: Kevva Decompress through 4.2.1 (unmaintained); @xhmikosr/decompress (npm) SEMVER:introduced=11.0.0,fixed=11.1.4; decompress (npm) SEMVER:introduced=0,last_affected=4.2.1; XhmikosR Decompress before 10.2.2 and 11.1.4.
Is there a fix for CVE-2026-101894?: Yes. @xhmikosr/decompress (npm): upgrade to 11.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101894 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-101894?: Check whether you run Kevva Decompress, @xhmikosr/decompress (npm), decompress (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@xhmikosr/decompress (npm): upgrade to 11.1.4 or later
```
npm install @xhmikosr/decompress@11.1.4
```

Technical details

The vulnerability exploits a symlink chain bypass in the decompress API's lexical containment checks. An attacker supplies a crafted archive with chained symlink entries that, when followed by the kernel, resolve outside the output directory. This allows path traversal attacks that can read or write files outside the extraction scope. The flaw is a bypass of incomplete hardening from a prior fix.

Affected products

XhmikosR decompress before 10.2.2 and 11.1.4
kevva decompress through 4.2.1 (unmaintained)

Identifiers

CVE-2026-101894
GHSA-hrh2-vp3x-79xf

Timeline

2026-09-28: disclosed: CVE-2026-101894 published
2026-08-05: patched: @xhmikosr/decompress patched in versions 10.2.2 and 11.1.4

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.