Skip to main content
Mallory
HighVulnerability

CVE-2026-17524: Directory Traversal in zip-lib Extraction

Published Jul 28, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.7High · v4
EPSS1.2%67th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-17524CWE-22 · Improper Limitation of a Pathname…

CVE-2026-17524 is a directory traversal vulnerability in zip-lib affecting versions prior to 1.1.0. The flaw is in the archive extraction logic’s caching mechanism for path validation. During extraction, the security check intended to ensure output paths remain within the target directory only evaluates and caches path status when the initial directory symlink is created during the first extraction. Because subsequent extraction behavior can rely on this cached result, an attacker can bypass the intended isOutsideTargetFolder protection and cause archive contents to be extracted outside the designated destination.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to bypass directory traversal protections during archive extraction and write files outside the intended target folder. Based on the available severity information, the primary impact is unauthorized file write leading to potential exposure of sensitive data or placement of attacker-controlled content in unintended filesystem locations.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, avoid extracting untrusted archives with affected versions of zip-lib. Restrict extraction operations to trusted inputs only and isolate extraction into tightly controlled environments with minimal filesystem permissions so that unintended writes outside the destination directory cannot affect sensitive locations.

Remediation

Patch, then assume compromise.

Upgrade zip-lib to version 1.1.0 or later, which contains the fix for the path validation caching flaw in the extraction process.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-17524 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-17524 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-17524?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-17524.
Is there a patch for CVE-2026-17524?
Upgrade zip-lib to version 1.1.0 or later, which contains the fix for the path validation caching flaw in the extraction process.
How severe is CVE-2026-17524?
CVE-2026-17524 has a CVSS v4 score of 8.7 (High) and an EPSS score of 1.2% (67th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.