NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
MEDIUM severity

Directory Traversal in SharpCompressGHSA-fxh6-w476-hgr4

MEDIUMFix: adamhathcock/sharpcompress#374

GHSA-fxh6-w476-hgr4 is a medium-severity (CVSS 5.5) Path Traversal vulnerability in SharpCompress. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for SharpCompress — see the affected versions and patch details below.

Also known asCVE-2018-1002206SNYK-DOTNET-SHARPCOMPRESS-60246
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
9.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk
0.22%4.28%8.35%12.4%2.5%9.3%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
.NETSharpCompress

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

SharpCompress before 0.21.0 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetSharpCompressall versions0.21.0dotnet add package SharpCompress --version 0.21.0

Affected Products

1 product · 1 configurations
Application
sharpcompressadamhathcock
< 0.21.0
range
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update SharpCompress to 0.21.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fxh6-w476-hgr4 is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

SharpCompress prior to version 0.21 is vulnerable to path traversal issue in archive extraction.
O3 Security · Impact-Aware SCA

Is GHSA-fxh6-w476-hgr4 in your dependencies?

Find it across NuGet, including transitive dependencies.

Directory Traversal in SharpCompress (Medium 5.5)