VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.gradle.publish:plugin-publish-plugin: vulnerability history, versions and safety

com.gradle.publish:plugin-publish-plugin is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 13 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all com.gradle.publish:plugin-publish-plugin vulnerabilities

Vulert verdict on com.gradle.publish:plugin-publish-plugin 2.2.1 i

Updated on 23 Oct 2026

Good news: 2.2.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

What to do: Stay on 2.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.2.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 91 packages i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for com.gradle.publish:plugin-publish-plugin, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.2.1 10 Sep 2026 none Apache-2.0 — Details →
2.1.1 19 Mar 2026 none Apache-2.0 — Details →
2.1.0 04 Mar 2026 none Apache-2.0 — Details →
2.0.0 03 Sep 2025 none Apache-2.0 — Details →
1.3.1 30 Jan 2025 none — — Details →
1.3.0 11 Sep 2024 none — — Details →
1.2.2 29 Aug 2024 none — — Details →
1.2.1 17 Aug 2023 none — — Details →
1.2.0 07 Apr 2023 none — — Details →
1.1.0 11 Nov 2022 none — — Details →
1.0.0 29 Jun 2022 none — — Details →
1.0.0-rc-3 13 Jun 2022 none — — Details →
1.0.0-rc-2 13 May 2022 none — — Details →
1.0.0-rc-1 05 Apr 2022 none — — Details →
0.21.0 30 Mar 2022 none — — Details →
0.20.0 19 Jan 2022 none — — Details →
0.19.0 29 Dec 2021 none — — Details →
0.18.0 16 Nov 2021 none — — Details →
0.17.0 05 Nov 2021 none — — Details →
0.16.0 14 Sep 2021 none — — Details →
0.15.0 20 May 2021 none — — Details →
0.14.0 31 Mar 2021 none — — Details →
0.13.0 19 Feb 2021 none — — Details →
0.12.0 26 May 2020 none — — Details →
0.11.0 27 Mar 2020 none — — Details →
0.10.1 01 Feb 2019 M1 — Yes Details →
0.10.0 27 Jul 2018 M1 — Yes Details →
0.9.10 07 Feb 2018 M1 — Yes Details →
0.9.9 20 Oct 2017 M1 — Yes Details →
0.9.8 28 Sep 2017 M1 — Yes Details →
0.9.7 05 Dec 2016 M1 — Yes Details →
0.9.4 02 Dec 2016 M1 — Yes Details →
0.9.5 02 Dec 2016 M1 — Yes Details →
0.9.6 02 Dec 2016 M1 — Yes Details →
0.9.0 02 Dec 2016 M1 — Yes Details →
0.9.1 02 Dec 2016 M1 — Yes Details →
0.9.2 02 Dec 2016 M1 — Yes Details →
0.9.3 02 Dec 2016 M1 — Yes Details →

All 38 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for com.gradle.publish:plugin-publish-plugin

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2020-7599: Exposure of Sensitive Information in Gradle publish plugin 6.5 medium 0.11.0 24 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About com.gradle.publish:plugin-publish-plugin

Is com.gradle.publish:plugin-publish-plugin safe to use?

Vulert records 1 vulnerabilities for com.gradle.publish:plugin-publish-plugin in Maven: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is com.gradle.publish:plugin-publish-plugin's Vulert package health score?

Vulert scores com.gradle.publish:plugin-publish-plugin 89/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of com.gradle.publish:plugin-publish-plugin affected?

No. 2.2.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of com.gradle.publish:plugin-publish-plugin should I use?

2.2.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does com.gradle.publish:plugin-publish-plugin have?

1 vulnerability is recorded for com.gradle.publish:plugin-publish-plugin in the Maven ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.gradle.publish:plugin-publish-plugin vulnerabilities disclosed?

0 vulnerabilities were recorded for com.gradle.publish:plugin-publish-plugin in the last 12 months, and the oldest entry in this database dates to 24 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of com.gradle.publish:plugin-publish-plugin are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor com.gradle.publish:plugin-publish-plugin for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.gradle.publish:plugin-publish-plugin version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.