<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-11T09:06:12.727861+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-75598</id>
    <title>fkie_cve-2026-75598</title>
    <updated>2026-11-11T09:06:12.731271+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-75598"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-rr8v-fxxf-c986</id>
    <title>GHSA-rr8v-fxxf-c986 — Gradle Shadow: Zip Slip path traversal in ShadowCopyAction — no independent entry-name sanitization</title>
    <updated>2026-11-11T09:06:12.731431+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: com.gradleup.shadow:com.gradleup.shadow.gradle.plugin</p>
<p>### Summary
ShadowCopyAction in the Shadow plugin does not validate or sanitize ZIP entry names before writing them to the output fat JAR. A malicious upstream dependency containing path traversal sequences (e.g. `../../../../tmp/pwned.txt`) in entry names will have those entries reproduced verbatim in the output shadow JAR.</p>
<p>### Details
The vulnerability exists because Shadow relies entirely on Gradle's ZipFileTree for entry sanitization rather than implementing its own path validation. This means:</p>
<p>1. Users on Gradle &lt; 7.6.2 / 8.x &lt; 8.2.0 are directly exploitable
2. The produced shadow JAR becomes a Zip Slip weapon against any 
downstream consumer using unprotected extraction (raw ZipInputStream, 
older CI tooling, custom Java unpackers)
3. If Shadow ever uses a non-ZipFileTree code path, protection 
disappears silently</p>
<p>Affected file: `src/main/kotlin/com/github/jengelman/gradle/plugins/shadow/internal/ShadowCopyAction.kt`</p>
<p>### PoC
1. Create a malicious JAR with path traversal entry:
```python
import zipfile
with zipfile.ZipFile('evil.jar', 'w') as zf:
    zf.writestr('../../../../tmp/zipslip_proof.txt', 'pwned')
```
2. Add as dependency in a shadow project
3. Run `gradle shadowJar`
4. Run `unzip -l build/libs/*.jar | grep "\.\."`
5. Traversal entry survives in output JAR</p>
<p>### Impact
Any tool extracting the shadow JAR with unprotected extraction is subject to arbitrary file overwrite. Users on older Gradle versions  are directly vulnerable at build time.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-rr8v-fxxf-c986"/>
  </entry>
</feed>
