Skip to main content
VulnerabilityPublished

CVE-2026-75598: GradleUp shadow · Path Traversal

Affects GradleUp shadowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 9.6.0 when convenient.

Data as of 6 Nov 2026, 18:10 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.3
Patch
Available – fixed in 9.6.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade GradleUp shadow to 9.6.0.

Affected software

ProductAffectedFixed in
GradleUpshadowAffected
  • <9.6.0
Fixed in
  • 9.6.0

AI-suggested

Upgrade the Gradle Shadow plugin to version 9.6.0 or later, where the vulnerability is fixed. Since some Shadow implementations process dependency archives directly, ensure that all components using Shadow are updated accordingly. Additionally, ensure that extraction processes enforce path traversal protections to prevent writing files outside intended directories. No other vendor advisory indicates that no action is required.

Description

CVE-2026-75598 is a path traversal vulnerability in the Gradle Shadow plugin versions prior to 9.6.0. The plugin fails to validate ZIP entry names before writing them to output archives, allowing malicious dependencies to include traversal paths. This can lead to files being written outside the intended extraction directory if the archive is extracted without proper path traversal protections. The issue is fixed in version 9.6.0.

References

Community reviews

Loading reviews…