Exposure of Sensitive Information in Gradle publish plugin

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2020-7599: 0.48% estimated exploitation activity in the next 30 days; percentile 41.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

All versions of com.gradle.plugin-publish before 0.11.0 are vulnerable to Insertion of Sensitive Information into Log File. When a plugin author publishes a Gradle plugin while running Gradle with the --info log level flag, the Gradle Logger logs an AWS pre-signed URL. If this build log is publicly visible (as it is in many popular public CI systems like TravisCI) this AWS pre-signed URL would allow a malicious actor to replace a recently uploaded plugin with their own.

Published by the source

24 May 2022, 17:12 UTC

Last modified by the source

27 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 16:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cv78-v957-jx34

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-7599

Advisory: Exposure of Sensitive Information in Gradle publish plugin
IDs: CVE-2020-7599, GHSA-cv78-v957-jx34
Record: https://patchnext.com/advisories/cve-2020-7599 (revision 1, source checked 26 Oct 2026, 16:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin 0.11.0; com.gradle.publish:plugin-publish-plugin 0.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin: affected < 0.11.0; fixed in 0.11.0
- Maven com.gradle.publish:plugin-publish-plugin: affected < 0.11.0; fixed in 0.11.0

## Suggested inspection (read-only)
- Maven com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin: check the installed version with your package manager.
- Maven com.gradle.publish:plugin-publish-plugin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin, com.gradle.publish:plugin-publish-plugin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cv78-v957-jx34 (GitHub-reviewed advisory GHSA-cv78-v957-jx34 lists affected ranges: Maven com.gradle.publish:plugin-publish-plugin >=0 =0 <0.11.0)

Commands are suggestions: review each one before running it.