Skip to content

← Actionable
Medium, CVSS 5.5

Improper Limitation of a Pathname to a Restricted Directory in SharpZipLib

CVE-2018-1002208GHSA-cqj4-m2pc-v9m5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (sharpziplib 1.0.0-rc1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • NuGet sharpziplib

    Affected
    <= 1.0.0-alpha2
    Fixed in
    1.0.0-rc1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.5 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS
  • CVE-2018-1002208: 9.88% estimated exploitation activity in the next 30 days; percentile 95.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

SharpZipLib before 1.0 RC1 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'.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-cqj4-m2pc-v9m5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-1002208

Advisory: Improper Limitation of a Pathname to a Restricted Directory in SharpZipLib
IDs: CVE-2018-1002208, GHSA-cqj4-m2pc-v9m5
Record: https://patchnext.com/advisories/cve-2018-1002208 (revision 1, source checked 26 Oct 2026, 16:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sharpziplib 1.0.0-rc1. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet sharpziplib: affected <= 1.0.0-alpha2; fixed in 1.0.0-rc1

## Suggested inspection (read-only)
- NuGet sharpziplib: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sharpziplib.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cqj4-m2pc-v9m5 (GitHub-reviewed advisory GHSA-cqj4-m2pc-v9m5 lists affected ranges: NuGet sharpziplib >=0 <=1.0.0-alpha2)

Commands are suggestions: review each one before running it.

Loading voting…