VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.junit.jupiter:junit-jupiter-api: vulnerability history, versions and safety

org.junit.jupiter:junit-jupiter-api is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

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.junit.jupiter:junit-jupiter-api vulnerabilities

Vulert verdict on org.junit.jupiter:junit-jupiter-api 6.1.3 i

Updated on 23 Oct 2026

Good news: 6.1.3, the version you would install today, has no known vulnerabilities.

Package health score 96/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

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

  • Current release 6.1.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 2,165 packages i
  • Stars 7,058 i
  • Last release 2 months ago i
  • Licence non-standard 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.junit.jupiter:junit-jupiter-api, 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
6.1.3 08 Aug 2026 none non-standard — Details →
6.1.2 12 Jul 2026 none non-standard — Details →
6.1.1 28 Jun 2026 none non-standard — Details →
6.1.0 19 May 2026 none non-standard — Details →
5.14.4 26 Apr 2026 none non-standard — Details →
6.1.0-RC1 25 Apr 2026 none non-standard — Details →
6.0.3 15 Feb 2026 none non-standard — Details →
5.14.3 15 Feb 2026 none non-standard — Details →
6.0.2 06 Jan 2026 none non-standard — Details →
5.14.2 06 Jan 2026 none non-standard — Details →
6.1.0-M1 17 Nov 2025 none non-standard — Details →
6.0.1 31 Oct 2025 none non-standard — Details →
5.14.1 31 Oct 2025 none non-standard — Details →
6.0.0 30 Sep 2025 none non-standard — Details →
5.14.0 30 Sep 2025 none non-standard — Details →
5.14.0-RC1 23 Sep 2025 none non-standard — Details →
6.0.0-RC3 14 Sep 2025 none non-standard — Details →
6.0.0-RC2 25 Aug 2025 none non-standard — Details →
6.0.0-RC1 20 Aug 2025 none non-standard — Details →
6.0.0-M2 22 Jul 2025 none non-standard — Details →
5.13.4 21 Jul 2025 none non-standard — Details →
5.13.3 04 Jul 2025 none non-standard — Details →
6.0.0-M1 27 Jun 2025 none non-standard — Details →
5.13.2 24 Jun 2025 none non-standard — Details →
5.13.1 07 Jun 2025 none non-standard — Details →
5.13.0 30 May 2025 none non-standard — Details →
5.13.0-RC1 16 May 2025 none non-standard — Details →
5.13.0-M3 02 May 2025 none non-standard — Details →
5.12.2 11 Apr 2025 none non-standard — Details →
5.13.0-M2 24 Mar 2025 none non-standard — Details →
5.13.0-M1 21 Mar 2025 none non-standard — Details →
5.12.1 14 Mar 2025 none non-standard — Details →
5.12.0 21 Feb 2025 none non-standard — Details →
5.12.0-RC2 12 Feb 2025 none non-standard — Details →
5.12.0-RC1 07 Feb 2025 none non-standard — Details →
5.12.0-M1 31 Jan 2025 none non-standard — Details →
5.11.4 16 Dec 2024 none non-standard — Details →
5.11.3 21 Oct 2024 none non-standard — Details →
5.11.2 04 Oct 2024 none non-standard — Details →
5.10.5 04 Oct 2024 none non-standard — Details →
5.11.1 25 Sep 2024 none non-standard — Details →
5.10.4 24 Sep 2024 none non-standard — Details →
5.11.0 14 Aug 2024 none non-standard — Details →
5.11.0-RC1 31 Jul 2024 none non-standard — Details →
5.10.3 27 Jun 2024 none non-standard — Details →
5.11.0-M2 17 May 2024 none non-standard — Details →
5.11.0-M1 23 Apr 2024 none non-standard — Details →
5.10.2 04 Feb 2024 none non-standard — Details →
5.10.1 05 Nov 2023 none non-standard — Details →
5.10.0 23 Jul 2023 none non-standard — Details →
5.10.0-RC2 19 Jul 2023 none non-standard — Details →
5.10.0-RC1 06 Jul 2023 none non-standard — Details →
5.10.0-M1 13 May 2023 none non-standard — Details →
5.9.3 26 Apr 2023 none non-standard — Details →
5.9.2 10 Jan 2023 none non-standard — Details →
5.9.1 20 Sep 2022 none non-standard — Details →
5.9.0 26 Jul 2022 none non-standard — Details →
5.9.0-RC1 04 Jul 2022 none non-standard — Details →
5.9.0-M1 15 May 2022 none non-standard — Details →
5.8.2 28 Nov 2021 none non-standard — Details →
5.8.1 22 Sep 2021 none non-standard — Details →
5.8.0 12 Sep 2021 none non-standard — Details →
5.8.0-RC1 17 Aug 2021 none non-standard — Details →
5.7.2 15 May 2021 none non-standard — Details →
5.8.0-M1 11 Feb 2021 none non-standard — Details →
5.7.1 04 Feb 2021 none non-standard — Details →
5.6.3 26 Oct 2020 none non-standard — Details →
5.7.0 13 Sep 2020 none non-standard — Details →
5.7.0-RC1 16 Aug 2020 none non-standard — Details →
5.7.0-M1 19 Apr 2020 none non-standard — Details →
5.6.2 10 Apr 2020 none non-standard — Details →
5.6.1 22 Mar 2020 none non-standard — Details →
5.6.0 20 Jan 2020 none non-standard — Details →
5.6.0-RC1 06 Jan 2020 none non-standard — Details →
5.6.0-M1 21 Oct 2019 none non-standard — Details →
5.5.2 08 Sep 2019 none non-standard — Details →
5.5.1 20 Jul 2019 none non-standard — Details →
5.5.0 30 Jun 2019 none non-standard — Details →
5.5.0-RC2 20 Jun 2019 none non-standard — Details →
5.5.0-RC1 06 Jun 2019 none non-standard — Details →
5.4.2 07 Apr 2019 none non-standard — Details →
5.5.0-M1 19 Mar 2019 none non-standard — Details →
5.4.1 17 Mar 2019 none non-standard — Details →
5.4.0 07 Feb 2019 none non-standard — Details →
5.4.0-RC2 31 Jan 2019 none non-standard — Details →
5.4.0-RC1 24 Jan 2019 none non-standard — Details →
5.4.0-M1 23 Dec 2018 none non-standard — Details →
5.3.2 25 Nov 2018 none non-standard — Details →
5.3.1 11 Sep 2018 none non-standard — Details →
5.3.0 03 Sep 2018 none non-standard — Details →
5.3.0-RC1 13 Aug 2018 none non-standard — Details →
5.3.0-M1 24 Jun 2018 none non-standard — Details →
5.2.0 29 Apr 2018 none non-standard — Details →
5.2.0-RC1 22 Apr 2018 none non-standard — Details →
5.2.0-M1 15 Apr 2018 none non-standard — Details →
5.1.1 08 Apr 2018 none non-standard — Details →
5.1.0 18 Feb 2018 none non-standard — Details →
5.1.0-RC1 04 Feb 2018 none non-standard — Details →
5.1.0-M2 28 Jan 2018 none non-standard — Details →
5.0.3 15 Jan 2018 none non-standard — Details →
5.1.0-M1 19 Nov 2017 none — — Details →
5.0.2 12 Nov 2017 none — — Details →
5.0.1 03 Oct 2017 none — — Details →
5.0.0 10 Sep 2017 none — — Details →
5.0.0-RC3 23 Aug 2017 none — — Details →
5.0.0-RC2 30 Jul 2017 none — — Details →
5.0.0-RC1 30 Jul 2017 none — — Details →
5.0.0-M6 18 Jul 2017 none — — Details →
5.0.0-M5 04 Jul 2017 none — — Details →
5.0.0-M4 01 Apr 2017 none — — Details →
5.0.0-M3 30 Nov 2016 none — — Details →
5.0.0-M2 23 Jul 2016 none — — Details →
5.0.0-M1 07 Jul 2016 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for org.junit.jupiter:junit-jupiter-api

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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.junit.jupiter:junit-jupiter-api

Is org.junit.jupiter:junit-jupiter-api safe to use?

Vulert has no vulnerabilities on record for org.junit.jupiter:junit-jupiter-api in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is org.junit.jupiter:junit-jupiter-api's Vulert package health score?

Vulert scores org.junit.jupiter:junit-jupiter-api 96/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 org.junit.jupiter:junit-jupiter-api affected?

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

6.1.3 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.junit.jupiter:junit-jupiter-api have?

0 vulnerabilities are recorded for org.junit.jupiter:junit-jupiter-api in the Maven ecosystem: 0 critical, 0 high, 0 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.junit.jupiter:junit-jupiter-api vulnerabilities disclosed?

0 vulnerabilities were recorded for org.junit.jupiter:junit-jupiter-api in the last 12 months. 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.junit.jupiter:junit-jupiter-api 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.junit.jupiter:junit-jupiter-api for upcoming vulnerabilities?

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