# Exposure of Sensitive Information in Gradle publish plugin

Advisory record · `GHSA-cv78-v957-jx34`

- **Identifiers:** `GHSA-cv78-v957-jx34` · `CVE-2020-7599`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-532](https://cwe.mitre.org/data/definitions/532.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 24 May 2022
- **Updated:** 13 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2022, 17:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.gradle.publish:plugin-publish-plugin` (Maven): affected `<0.11.0`; fixed in `0.11.0`
- `com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin` (Maven): affected `<0.11.0`; fixed in `0.11.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of the Gradle plugin publish plugin (com.gradle.publish:plugin-publish-plugin and com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin) before 0.11.0 log an AWS pre-signed URL when a plugin is published with the --info log level. If the build log is publicly visible, as in many public CI systems, an attacker who reads that URL could replace a recently uploaded plugin with their own. Upgrade to 0.11.0 or later. Avoid running publish tasks with --info on public CI until then.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0048, the 42nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-cv78-v957-jx34)

## Sources

- [GitHub Advisory Database: GHSA-cv78-v957-jx34](https://github.com/advisories/GHSA-cv78-v957-jx34)
- [OSV: GHSA-cv78-v957-jx34](https://osv.dev/vulnerability/GHSA-cv78-v957-jx34)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-7599>
- <https://blog.gradle.org/plugin-portal-update>
- <https://plugins.gradle.org/plugin/com.gradle.plugin-publish>
- <https://snyk.io/vuln/SNYK-JAVA-COMGRADLEPLUGINPUBLISH-559866>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cv78-v957-jx34>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cv78-v957-jx34/>. Everything for agents: <https://agentprime.io/llms.txt>.
