VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

junit:junit: vulnerability history, versions and safety

junit:junit is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 18 releases, first recorded in Oct 2020. 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 junit:junit vulnerabilities

Vulert verdict on junit:junit 4.13.2 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 4.13.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 12 Oct 2020 i
  • Highest CVSS 4.4 i
  • With no published fix 0 i
  • Depended on by 12,699 packages i
  • Stars 8,511 i
  • OpenSSF scorecard 5/10 i
  • Last release 68 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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 junit:junit, 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
4.13.2 13 Feb 2021 none non-standard — Details →
4.13.1 11 Oct 2020 none non-standard — Details →
4.13 01 Jan 2020 M1 non-standard Yes Details →
4.13-rc-2 01 Dec 2019 M1 non-standard Yes Details →
4.13-rc-1 26 Oct 2019 M1 non-standard Yes Details →
4.13-beta-3 05 May 2019 M1 non-standard Yes Details →
4.13-beta-2 02 Feb 2019 M1 non-standard Yes Details →
4.13-beta-1 25 Nov 2018 M1 non-standard Yes Details →
4.12 04 Dec 2014 M1 non-standard Yes Details →
4.12-beta-3 09 Nov 2014 M1 non-standard Yes Details →
4.12-beta-2 25 Sep 2014 M1 non-standard Yes Details →
4.12-beta-1 27 Jul 2014 M1 non-standard Yes Details →
4.11 14 Nov 2012 M1 non-standard Yes Details →
4.11-beta-1 15 Oct 2012 M1 non-standard Yes Details →
4.10 29 Sep 2011 M1 non-standard Yes Details →
4.9 22 Aug 2011 M1 non-standard Yes Details →
4.8.2 05 Oct 2010 M1 non-standard Yes Details →
4.8 05 Oct 2010 M1 non-standard Yes Details →
4.8.1 25 Feb 2010 M1 non-standard Yes Details →
4.7 12 Aug 2009 M1 non-standard Yes Details →
4.6 09 May 2009 none non-standard — Details →
4.5 08 Aug 2008 none non-standard — Details →
4.4 19 Jul 2007 none non-standard — Details →
4.3.1 29 Mar 2007 none non-standard — Details →
4.3 20 Mar 2007 none non-standard — Details →
4.2 16 Nov 2006 none non-standard — Details →
4.1 02 May 2006 none non-standard — Details →
3.8.2 03 Mar 2006 none non-standard — Details →
4.0 16 Feb 2006 none — — Details →
3.8 01 Aug 2005 none non-standard — Details →
3.7 01 Aug 2005 none non-standard — Details →
3.8.1 01 Aug 2005 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 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 junit:junit

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-15250: Information Disclosure Vulnerability in JUnit 4.4 medium 4.13.1 12 Oct 2020

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 junit:junit

Is junit:junit safe to use?

Vulert records 1 vulnerabilities for junit:junit 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 junit:junit's Vulert package health score?

Vulert scores junit:junit 76/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 junit:junit affected?

No. 4.13.2, 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 junit:junit should I use?

4.13.2 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 junit:junit have?

1 vulnerability is recorded for junit:junit 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 junit:junit vulnerabilities disclosed?

0 vulnerabilities were recorded for junit:junit in the last 12 months, and the oldest entry in this database dates to 12 Oct 2020. 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 junit:junit 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 junit:junit for upcoming vulnerabilities?

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