VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.jenkins-ci.plugins:release: vulnerability history, versions and safety

org.jenkins-ci.plugins:release is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 16 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
2 vulnerabilities recorded H1 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 org.jenkins-ci.plugins:release vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:release 2.19 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 2.19 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 24 i
  • Last release 3 months ago i
  • Licence MIT 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 org.jenkins-ci.plugins:release, 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.15 17 Jul 2026 none — — Details →
2.19 17 Jul 2026 none — — Details →
2.17 17 Jul 2026 none — — Details →
2.12 17 Jul 2026 none — — Details →
2.14 17 Jul 2026 none — — Details →
2.13 17 Jul 2026 none — — Details →
2.16 17 Jul 2026 none — — Details →
2.18 17 Jul 2026 none — — Details →
2.11 18 Dec 2020 none MIT — Details →
2.10.2 18 Nov 2018 M1 — Yes Details →
2.10.1 13 Mar 2018 M1 — Yes Details →
2.10 15 Jan 2018 M1 — Yes Details →
2.9 08 Dec 2017 H1 M1 — Yes Details →
2.8 27 Jun 2017 H1 M1 — Yes Details →
2.7 08 Apr 2017 H1 M1 — Yes Details →
2.6.1 14 Oct 2016 H1 M1 — Yes Details →
2.6 29 Sep 2016 H1 M1 — Yes Details →
2.5.4 26 Oct 2015 H1 M1 — Yes Details →
2.5.3 24 Apr 2015 H1 M1 — Yes Details →
2.4.1 27 Sep 2013 H1 M1 — Yes Details →
2.4 04 Aug 2013 H1 M1 — Yes Details →
2.3 19 Sep 2012 H1 M1 — Yes Details →
2.2 14 Sep 2011 H1 M1 — Yes Details →
2.1 13 Mar 2011 H1 M1 — Yes Details →
2.0 16 Feb 2011 H1 M1 — Yes Details →

All 25 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 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:release

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1000013: CSRF vulnerability in Jenkins Release plugin 8.8 high 2.10 14 May 2022
CVE-2020-2292: Stored XSS vulnerability in Jenkins Release Plugin 5.4 medium 2.11 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 org.jenkins-ci.plugins:release

Is org.jenkins-ci.plugins:release safe to use?

Vulert records 2 vulnerabilities for org.jenkins-ci.plugins:release in Maven: 0 critical, 1 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 org.jenkins-ci.plugins:release's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:release 73/100, which reads as in good shape. 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 org.jenkins-ci.plugins:release affected?

No. 2.19, 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 org.jenkins-ci.plugins:release should I use?

2.19 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 org.jenkins-ci.plugins:release have?

2 vulnerabilities are recorded for org.jenkins-ci.plugins:release in the Maven ecosystem: 0 critical, 1 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 org.jenkins-ci.plugins:release vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jenkins-ci.plugins:release in the last 12 months, and the oldest entry in this database dates to 14 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 org.jenkins-ci.plugins:release 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 org.jenkins-ci.plugins:release for upcoming vulnerabilities?

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