Gradle Shadow: Zip Slip path traversal in ShadowCopyAction — no independent entry-name sanitization
- Exploited
- No known exploitation
- Fix
- Fixed in 9.6.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 9.6.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Gradle Shadow plugin, which builds fat or uber JARs, does not check ZIP entry names before writing them to its output archive, so a malicious dependency can carry path-traversal entry names into that archive. A local attacker with no login can cause attacker-controlled files to be written outside the intended destination when a user extracts the archive without path traversal protection, and user interaction is needed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The Gradle Shadow plugin creates fat or uber JARs and supports file transformation and package relocation. Prior to version 9.6.0, Shadow does not independently validate ZIP entry names before writing them to its output archive. A malicious dependency can cause traversal entry names to be preserved when the applicable archive-processing path does not reject them. Some affected Shadow implementations process dependency archives directly, so upgrading Gradle alone does not universally prevent this behavior. If the resulting archive is extracted without path traversal protection, attacker-controlled files can be written outside the intended destination. This issue is fixed in version 9.6.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 9.6.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- GradleUp shadow
fixed in 9.6.0
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-75598
Is CVE-2026-75598 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-75598?
shadow: before 9.6.0.Source: cve.now feed data
How do I fix CVE-2026-75598?
Upgrade to a fixed version: 9.6.0.Source: cve.now feed data