How severe is GHSA-hrh2-vp3x-79xf?

GHSA-hrh2-vp3x-79xf has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-hrh2-vp3x-79xf?

GHSA-hrh2-vp3x-79xf affects the following packages: @xhmikosr/decompress (npm), @xhmikosr/decompress (npm), decompress (npm). Ecosystems affected: npm.

How do I fix GHSA-hrh2-vp3x-79xf?

Update @xhmikosr/decompress to 11.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrh2-vp3x-79xf is resolved across your whole dependency graph.

How do I detect GHSA-hrh2-vp3x-79xf in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @xhmikosr/decompress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hrh2-vp3x-79xf if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-hrh2-vp3x-79xf actively exploited in the wild?

No public exploit code has been indexed for GHSA-hrh2-vp3x-79xf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hrh2-vp3x-79xf?

GHSA-hrh2-vp3x-79xf has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hrh2-vp3x-79xf?

GHSA-hrh2-vp3x-79xf is classified as Path Traversal (CWE-22), CWE-59 (CWE-59). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-hrh2-vp3x-79xf published, and has it been updated?

GHSA-hrh2-vp3x-79xf was published on September 29, 2026 and was last updated on September 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

@xhmikosr/decompress: Path traversal via symlink chainGHSA-hrh2-vp3x-79xf

CRITICALFix: XhmikosR/decompress@5f4b2f6

GHSA-hrh2-vp3x-79xf is a critical-severity (CVSS 9.1) Path Traversal vulnerability in @xhmikosr/decompress. A fix is available for @xhmikosr/decompress — see the affected versions and patch details below.

Also known asCVE-2026-101894

Published

Sep 29, 2026

Updated

Sep 30, 2026

Affected

3 pkgs

Patched

2 / 3

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hrh2-vp3x-79xf.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-hrh2-vp3x-79xf by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

22other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@xhmikosr/decompressnpm

3.6Mdownloads / week

decompressnpm

1.8Mdownloads / week

Description

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/[email protected] (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.

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@xhmikosr/decompress`	≥ 11.0.0&&< 11.1.4	11.1.4`npm install @xhmikosr/decompress@11.1.4`
📦npm	`@xhmikosr/decompress`	all versions	10.2.2`npm install @xhmikosr/decompress@10.2.2`
📦npm	`decompress`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @xhmikosr/decompress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @xhmikosr/decompress to 11.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrh2-vp3x-79xf is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

A flaw was found in the @xhmikosr/decompress npm package for Node.js. The default decompress(input, output) API relies on lexical containment checks that do not account for the kernel following a planted symlink chain. An attacker can supply a crafted archive containing chained symlink entries so that a later entry…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-hrh2-vp3x-79xf (CC BY 4.0)

Frequently Asked Questions

### 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-control