Vulnerability Database · Maven · Package report

org.springframework.batch:spring-batch-core: vulnerability history, versions and safety

org.springframework.batch:spring-batch-core is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 58 releases, from Jan 2019 to 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 L1
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.

Vulert verdict on org.springframework.batch:spring-batch-core 6.1.0-RC1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 6.1.0-RC1 — unaffected i
  • Vulnerabilities on record 2 over 3 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Stars 2,965 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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 org.springframework.batch:spring-batch-core, 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.0.6 22 Oct 2026 none Apache-2.0 — Details →
6.1.0-RC1 22 Oct 2026 none Apache-2.0 — Details →
6.1.0-M2 24 Sep 2026 none Apache-2.0 — Details →
6.0.5 20 Aug 2026 none Apache-2.0 — Details →
6.1.0-M1 20 Aug 2026 none Apache-2.0 — Details →
6.0.4 10 Jun 2026 none Apache-2.0 — Details →
5.2.6 10 Jun 2026 none Apache-2.0 — Details →
5.2.5 18 Mar 2026 none Apache-2.0 — Details →
6.0.3 18 Mar 2026 none Apache-2.0 — Details →
6.0.2 21 Jan 2026 none Apache-2.0 — Details →
6.0.1 17 Dec 2025 none Apache-2.0 — Details →
6.0.0 19 Nov 2025 none Apache-2.0 — Details →
6.0.0-RC2 05 Nov 2025 none Apache-2.0 — Details →
6.0.0-RC1 22 Oct 2025 none Apache-2.0 — Details →
5.2.4 22 Oct 2025 none Apache-2.0 — Details →
6.0.0-M4 09 Oct 2025 none Apache-2.0 — Details →
5.2.3 17 Sep 2025 none Apache-2.0 — Details →
6.0.0-M3 17 Sep 2025 none Apache-2.0 — Details →
6.0.0-M2 20 Aug 2025 none Apache-2.0 — Details →
6.0.0-M1 23 Jul 2025 none Apache-2.0 — Details →
5.2.2 19 Mar 2025 none Apache-2.0 — Details →
5.1.3 19 Dec 2024 none Apache-2.0 — Details →
5.2.1 18 Dec 2024 none Apache-2.0 — Details →
5.2.0 21 Nov 2024 none Apache-2.0 — Details →
5.1.2 22 May 2024 none Apache-2.0 — Details →
5.0.6 22 May 2024 none Apache-2.0 — Details →
5.1.1 21 Feb 2024 none Apache-2.0 — Details →
5.0.5 21 Feb 2024 none Apache-2.0 — Details →
5.0.4 22 Nov 2023 none Apache-2.0 — Details →
5.1.0 22 Nov 2023 none Apache-2.0 — Details →
4.3.10 22 Nov 2023 none Apache-2.0 — Details →
5.0.3 23 Aug 2023 none Apache-2.0 — Details →
4.3.9 23 Aug 2023 none Apache-2.0 — Details →
5.0.2 17 May 2023 none Apache-2.0 — Details →
5.0.1 22 Feb 2023 none Apache-2.0 — Details →
4.3.8 22 Feb 2023 none Apache-2.0 — Details →
5.0.0 24 Nov 2022 none Apache-2.0 — Details →
4.3.7 22 Sep 2022 none Apache-2.0 — Details →
4.3.6 18 May 2022 none Apache-2.0 — Details →
4.3.5 23 Feb 2022 none Apache-2.0 — Details →
4.2.8.RELEASE 17 Nov 2021 none Apache-2.0 — Details →
4.3.4 17 Nov 2021 none Apache-2.0 — Details →
4.3.3 19 May 2021 none Apache-2.0 — Details →
4.2.7.RELEASE 19 May 2021 none Apache-2.0 — Details →
4.3.2 18 Mar 2021 none Apache-2.0 — Details →
4.2.6.RELEASE 17 Mar 2021 none Apache-2.0 — Details →
4.3.1 09 Dec 2020 none Apache-2.0 — Details →
4.2.5.RELEASE 09 Dec 2020 none Apache-2.0 — Details →
4.3.0 28 Oct 2020 none Apache-2.0 — Details →
4.2.4.RELEASE 11 Jun 2020 none Apache-2.0 — Details →
4.2.3.RELEASE 10 Jun 2020 H1 Apache-2.0 Yes Details →
4.2.2.RELEASE 01 Apr 2020 H1 Apache-2.0 Yes Details →
4.1.4.RELEASE 01 Apr 2020 H1 Apache-2.0 Yes Details →
4.2.1.RELEASE 04 Dec 2019 H1 Apache-2.0 Yes Details →
4.1.3.RELEASE 04 Dec 2019 H1 Apache-2.0 Yes Details →
4.0.4.RELEASE 03 Dec 2019 H1 Apache-2.0 Yes Details →
4.2.0.RELEASE 01 Oct 2019 H1 Apache-2.0 Yes Details →
4.1.2.RELEASE 03 Apr 2019 H1 Apache-2.0 Yes Details →
4.0.3.RELEASE 03 Apr 2019 H1 Apache-2.0 Yes Details →
4.0.2.RELEASE 11 Jan 2019 H1 Apache-2.0 Yes Details →
4.1.1.RELEASE 11 Jan 2019 H1 Apache-2.0 Yes Details →
3.0.10.RELEASE 11 Jan 2019 L1 Apache-2.0 Yes Details →
4.1.0.RELEASE 29 Oct 2018 H1 Apache-2.0 Yes Details →
3.0.9.RELEASE 07 Mar 2018 L1 Apache-2.0 Yes Details →
4.0.1.RELEASE 06 Mar 2018 H1 Apache-2.0 Yes Details →
4.0.0.RELEASE 01 Dec 2017 H1 Apache-2.0 Yes Details →
3.0.8.RELEASE 19 Jul 2017 L1 Apache-2.0 Yes Details →
3.0.7.RELEASE 22 Apr 2016 L1 Apache-2.0 Yes Details →
3.0.6.RELEASE 10 Dec 2015 L1 Apache-2.0 Yes Details →
3.0.5.RELEASE 10 Aug 2015 L1 Apache-2.0 Yes Details →
3.0.4.RELEASE 19 May 2015 L1 Apache-2.0 Yes Details →
3.0.3.RELEASE 15 Jan 2015 L1 Apache-2.0 Yes Details →
3.0.2.RELEASE 28 Oct 2014 L1 Apache-2.0 Yes Details →
3.0.1.RELEASE 07 Jul 2014 L1 Apache-2.0 Yes Details →
3.0.0.RELEASE 22 May 2014 L1 Apache-2.0 Yes Details →
2.2.7.RELEASE 22 May 2014 L1 Apache-2.0 Yes Details →
2.2.6.RELEASE 11 Apr 2014 L1 Apache-2.0 Yes Details →
2.2.5.RELEASE 21 Feb 2014 L1 Apache-2.0 Yes Details →
2.2.4.RELEASE 27 Dec 2013 L1 Apache-2.0 Yes Details →
2.2.3.RELEASE 22 Nov 2013 L1 Apache-2.0 Yes Details →
2.2.2.RELEASE 08 Sep 2013 L1 Apache-2.0 Yes Details →
2.2.1.RELEASE 26 Jul 2013 L1 Apache-2.0 Yes Details →
2.2.0.RELEASE 05 Jun 2013 L1 Apache-2.0 Yes Details →
2.1.9.RELEASE 20 Aug 2012 L1 Apache-2.0 Yes Details →
2.1.8.RELEASE 01 Jun 2011 L1 Apache-2.0 Yes Details →
2.1.7.RELEASE 21 Mar 2011 L1 Apache-2.0 Yes Details →
2.1.6.RELEASE 07 Feb 2011 L1 Apache-2.0 Yes Details →
2.1.5.RELEASE 12 Nov 2010 L1 — Yes Details →
2.1.4.RELEASE 08 Nov 2010 L1 — Yes Details →
2.1.3.RELEASE 07 Sep 2010 L1 — Yes Details →
2.1.2.RELEASE 09 Jul 2010 L1 — Yes Details →
2.1.1.RELEASE 23 Apr 2010 L1 — Yes Details →
2.1.0.RELEASE 04 Feb 2010 L1 — Yes Details →
2.1.0.M2 10 Nov 2009 L1 — Yes Details →
2.0.4.RELEASE 19 Oct 2009 L1 — Yes Details →
2.0.3.RELEASE 23 Aug 2009 L1 — Yes Details →
2.0.2.RELEASE 21 Jul 2009 L1 — Yes Details →
2.0.1.RELEASE 02 Jun 2009 L1 — Yes Details →
2.0.0.RELEASE 11 Apr 2009 L1 — Yes Details →
2.0.0.RC1 22 Feb 2009 L1 — Yes Details →
1.1.4.RELEASE 29 Jan 2009 L1 — Yes Details →
1.1.3.RELEASE-A 03 Nov 2008 L1 — Yes Details →
1.1.3.RELEASE 31 Oct 2008 L1 — Yes Details →
1.1.2.RELEASE 14 Aug 2008 L1 — Yes Details →
1.1.1.RELEASE 31 Jul 2008 L1 — Yes Details →
1.1.0.RELEASE 21 Jul 2008 L1 — Yes Details →
1.0.1.RELEASE 06 May 2008 L1 — Yes Details →
1.0.0.FINAL 28 Mar 2008 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2022 1

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.springframework.batch:spring-batch-core

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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.springframework.batch:spring-batch-core

Is org.springframework.batch:spring-batch-core safe to use?

Vulert records 2 vulnerabilities for org.springframework.batch:spring-batch-core in Maven: 0 critical, 1 high, 0 medium and 1 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.springframework.batch:spring-batch-core's Vulert package health score?

Vulert scores org.springframework.batch:spring-batch-core 85/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.springframework.batch:spring-batch-core affected?

No. 6.1.0-RC1, 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.

How many vulnerabilities does org.springframework.batch:spring-batch-core have?

2 vulnerabilities are recorded for org.springframework.batch:spring-batch-core in the Maven ecosystem: 0 critical, 1 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.springframework.batch:spring-batch-core vulnerabilities disclosed?

0 vulnerabilities were recorded for org.springframework.batch:spring-batch-core in the last 12 months, and the oldest entry in this database dates to 25 Jan 2019. 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.springframework.batch:spring-batch-core 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.springframework.batch:spring-batch-core for upcoming vulnerabilities?

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