CVE-2026-75598 · Package
NO FIX YET · SEE WHAT TO DO
The Gradle Shadow plugin, which builds fat or uber JARs, does not validate ZIP entry names before writing them, so path traversal names from a malicious dependency can be kept in the output archive. If that archive is extracted without path traversal protection, an attacker can write files to locations outside the intended destination.
first public Jul 16, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Projects that use the Gradle Shadow plugin to build fat or uber JARs, especially when they pull in third-party dependencies that could be malicious and when the resulting archive is extracted by another tool or process. Projects that do not use Shadow, or that never extract its output without path traversal protection, are less exposed. The sources note that upgrading Gradle alone does not fully prevent the behavior in some Shadow implementations, so the plugin version itself matters.
Not affected if no-shadow-plugin, output-never-extracted, path-traversal-protection-in-place
Who cares build-tooling, gradle, java, jvm, kotlin
plugins { id 'com.gradleup.shadow' version '...' }) and compare it with 9.6.09.6.0The 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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.