VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

org.springframework.security:spring-security-core is a package in the Maven ecosystem. Vulert records 28 vulnerabilities for it across 120 releases, from Oct 2018 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
28 vulnerabilities recorded C3 H10 M14 L1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 22 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.springframework.security:spring-security-core vulnerabilities

Vulert verdict on org.springframework.security:spring-security-core 7.2.0-RC1 i

Updated on 22 Oct 2026

Careful: 7.2.0-RC1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 7.2.0-RC1 — affected i
  • Vulnerabilities on record 28 over 7 years · 3 in the last year i
  • Latest disclosure 22 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 9,651 i
  • OpenSSF scorecard 6/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.security:spring-security-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
7.0.8 22 Oct 2026 L1 Apache-2.0 No Details →
7.1.2 22 Oct 2026 L1 Apache-2.0 No Details →
7.2.0-RC1 22 Oct 2026 L1 Apache-2.0 No Details →
7.2.0-M2 24 Sep 2026 L1 Apache-2.0 No Details →
7.0.7 20 Aug 2026 L1 Apache-2.0 No Details →
7.1.1 20 Aug 2026 L1 Apache-2.0 No Details →
7.2.0-M1 20 Aug 2026 L1 Apache-2.0 No Details →
7.1.0 09 Jun 2026 L1 Apache-2.0 No Details →
7.0.6 09 Jun 2026 L1 Apache-2.0 No Details →
6.5.11 09 Jun 2026 L1 Apache-2.0 No Details →
7.0.5 20 Apr 2026 L1 Apache-2.0 No Details →
7.1.0-RC1 20 Apr 2026 L1 Apache-2.0 No Details →
6.5.10 20 Apr 2026 L1 Apache-2.0 No Details →
7.0.4 16 Mar 2026 L1 Apache-2.0 No Details →
7.1.0-M3 16 Mar 2026 L1 Apache-2.0 No Details →
6.5.9 16 Mar 2026 M1 Apache-2.0 Yes Details →
6.5.8 13 Feb 2026 M1 Apache-2.0 Yes Details →
7.1.0-M2 13 Feb 2026 L1 Apache-2.0 No Details →
7.0.3 13 Feb 2026 L1 Apache-2.0 No Details →
7.1.0-M1 19 Jan 2026 L1 Apache-2.0 No Details →
7.0.2 15 Dec 2025 L1 Apache-2.0 No Details →
7.0.1 15 Dec 2025 L1 Apache-2.0 No Details →
6.5.7 17 Nov 2025 M1 Apache-2.0 Yes Details →
6.4.13 17 Nov 2025 L1 Apache-2.0 No Details →
7.0.0 17 Nov 2025 L1 Apache-2.0 No Details →
7.0.0-RC3 06 Nov 2025 L1 Apache-2.0 No Details →
7.0.0-RC2 04 Nov 2025 L1 Apache-2.0 No Details →
7.0.0-RC1 20 Oct 2025 L1 Apache-2.0 No Details →
6.4.12 20 Oct 2025 L1 Apache-2.0 No Details →
6.5.6 20 Oct 2025 M1 Apache-2.0 Yes Details →
6.4.11 17 Sep 2025 L1 Apache-2.0 No Details →
6.5.5 17 Sep 2025 M1 Apache-2.0 Yes Details →
7.0.0-M3 15 Sep 2025 L1 Apache-2.0 No Details →
6.5.4 15 Sep 2025 M1 Apache-2.0 Yes Details →
6.4.10 15 Sep 2025 L1 Apache-2.0 No Details →
7.0.0-M2 18 Aug 2025 L1 Apache-2.0 No Details →
6.4.9 18 Aug 2025 H1 Apache-2.0 Yes Details →
6.5.3 18 Aug 2025 M1 Apache-2.0 Yes Details →
6.4.8 21 Jul 2025 H1 Apache-2.0 Yes Details →
6.5.2 21 Jul 2025 M1 Apache-2.0 Yes Details →
7.0.0-M1 21 Jul 2025 L1 Apache-2.0 No Details →
6.4.7 16 Jun 2025 H1 Apache-2.0 Yes Details →
6.5.1 16 Jun 2025 M1 Apache-2.0 Yes Details →
6.3.10 16 Jun 2025 L1 Apache-2.0 No Details →
6.4.6 19 May 2025 H1 Apache-2.0 Yes Details →
6.5.0 19 May 2025 M1 Apache-2.0 Yes Details →
6.4.5 21 Apr 2025 H1 Apache-2.0 Yes Details →
6.3.9 21 Apr 2025 L1 Apache-2.0 No Details →
6.4.4 17 Mar 2025 H1 Apache-2.0 Yes Details →
6.3.8 17 Mar 2025 M1 Apache-2.0 Yes Details →
6.4.3 18 Feb 2025 H1 M1 Apache-2.0 Yes Details →
6.3.7 18 Feb 2025 L1 Apache-2.0 No Details →
6.4.2 16 Dec 2024 H1 M1 Apache-2.0 Yes Details →
6.3.6 16 Dec 2024 L1 Apache-2.0 No Details →
6.4.1 20 Nov 2024 H1 M1 Apache-2.0 Yes Details →
5.7.14 18 Nov 2024 L1 Apache-2.0 No Details →
5.8.16 18 Nov 2024 L1 Apache-2.0 No Details →
6.4.0 18 Nov 2024 H1 M1 Apache-2.0 Yes Details →
6.3.5 18 Nov 2024 L1 Apache-2.0 No Details →
6.2.8 18 Nov 2024 L1 Apache-2.0 No Details →
5.7.13 21 Oct 2024 M1 L1 Apache-2.0 No Details →
5.8.15 21 Oct 2024 L1 Apache-2.0 No Details →
6.2.7 21 Oct 2024 L1 Apache-2.0 No Details →
6.3.4 21 Oct 2024 L1 Apache-2.0 No Details →
6.3.3 21 Aug 2024 L1 Apache-2.0 No Details →
6.3.2 19 Aug 2024 L1 Apache-2.0 No Details →
6.2.6 19 Aug 2024 L1 Apache-2.0 No Details →
5.8.14 19 Aug 2024 L1 Apache-2.0 No Details →
6.2.5 17 Jun 2024 L1 Apache-2.0 No Details →
6.3.1 17 Jun 2024 M1 Apache-2.0 Yes Details →
5.8.13 17 Jun 2024 L1 Apache-2.0 No Details →
6.3.0 20 May 2024 M1 Apache-2.0 Yes Details →
6.2.4 15 Apr 2024 L1 Apache-2.0 No Details →
6.1.9 15 Apr 2024 L1 Apache-2.0 No Details →
5.8.12 15 Apr 2024 L1 Apache-2.0 No Details →
6.1.8 18 Mar 2024 L1 Apache-2.0 No Details →
6.2.3 18 Mar 2024 L1 Apache-2.0 No Details →
5.8.11 18 Mar 2024 L1 Apache-2.0 No Details →
5.7.12 18 Mar 2024 M1 L1 Apache-2.0 No Details →
5.8.10 16 Feb 2024 L1 Apache-2.0 No Details →
6.1.7 16 Feb 2024 L1 Apache-2.0 No Details →
6.2.2 16 Feb 2024 L1 Apache-2.0 No Details →
5.8.9 18 Dec 2023 L1 Apache-2.0 No Details →
6.1.6 18 Dec 2023 H1 Apache-2.0 Yes Details →
6.2.1 18 Dec 2023 L1 Apache-2.0 No Details →
6.2.0 20 Nov 2023 L1 Apache-2.0 No Details →
5.8.8 16 Oct 2023 L1 Apache-2.0 No Details →
6.0.8 16 Oct 2023 L1 Apache-2.0 No Details →
6.1.5 16 Oct 2023 H1 Apache-2.0 Yes Details →
5.8.7 18 Sep 2023 L1 Apache-2.0 No Details →
5.7.11 18 Sep 2023 H1 M1 L1 Apache-2.0 No Details →
6.0.7 18 Sep 2023 L1 Apache-2.0 No Details →
6.1.4 18 Sep 2023 H1 Apache-2.0 Yes Details →
6.1.3 21 Aug 2023 H1 Apache-2.0 Yes Details →
5.8.6 21 Aug 2023 L1 Apache-2.0 No Details →
6.0.6 21 Aug 2023 L1 Apache-2.0 No Details →
6.1.2 17 Jul 2023 H1 Apache-2.0 Yes Details →
6.0.5 17 Jul 2023 L1 Apache-2.0 No Details →
5.7.10 17 Jul 2023 H1 M1 L1 Apache-2.0 No Details →
5.8.5 17 Jul 2023 L1 Apache-2.0 No Details →
5.6.12 17 Jul 2023 H1 M1 — Yes Details →
5.6.11 19 Jun 2023 H1 M1 — Yes Details →
5.7.9 19 Jun 2023 H1 M1 L1 — No Details →
6.0.4 19 Jun 2023 L1 — No Details →
5.8.4 19 Jun 2023 L1 — No Details →
6.1.1 19 Jun 2023 H1 — Yes Details →
6.1.0 15 May 2023 H1 — Yes Details →
5.8.3 17 Apr 2023 L1 — No Details →
6.0.3 17 Apr 2023 L1 — No Details →
5.7.8 17 Apr 2023 H1 M1 L1 — No Details →
5.4.11 20 Mar 2023 H1 M2 — Yes Details →
5.7.7 21 Feb 2023 H1 M2 L1 — No Details →
6.0.2 21 Feb 2023 L1 — No Details →
5.8.2 21 Feb 2023 L1 — No Details →
5.8.1 19 Dec 2022 L1 — No Details →
5.6.10 19 Dec 2022 H1 M1 — Yes Details →
5.7.6 19 Dec 2022 H1 M2 L1 — No Details →
6.0.1 19 Dec 2022 L1 — No Details →
5.8.0 21 Nov 2022 L1 — No Details →
6.0.0 21 Nov 2022 L1 — No Details →

The newest 120 of 289 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2019 2
  • 2020 4
  • 2021 1
  • 2022 9
  • 2023 1
  • 2024 4
  • 2025 2
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for org.springframework.security:spring-security-core

The 5 most severe of 28 vulnerabilities recorded for this package

Search all 28 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-3527: Authorization Bypass in Spring Security 9.8 critical 3.1.7 15 Sep 2020
CVE-2022-31692: Spring Security authorization rules bypass via forward or include dispatcher types 9.8 critical 5.7.5 01 Nov 2022
CVE-2022-22978: Authorization bypass in Spring Security 9.8 critical 5.5.7 20 May 2022
CVE-2020-5407: Signature Wrapping Vulnerability in Spring Security 8.8 high 5.2.4 05 Jun 2020
CVE-2024-22257: Erroneous authentication pass in Spring Security 8.2 high 5.7.12 18 Mar 2024

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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

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

Vulert records 28 vulnerabilities for org.springframework.security:spring-security-core in Maven: 3 critical, 10 high, 14 medium and 1 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.springframework.security:spring-security-core's Vulert package health score?

Vulert scores org.springframework.security:spring-security-core 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of org.springframework.security:spring-security-core affected?

Yes. 7.2.0-RC1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

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

28 vulnerabilities are recorded for org.springframework.security:spring-security-core in the Maven ecosystem: 3 critical, 10 high, 14 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.security:spring-security-core vulnerabilities disclosed?

3 vulnerabilities were recorded for org.springframework.security:spring-security-core in the last 12 months, and the oldest entry in this database dates to 17 Oct 2018. 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.security:spring-security-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.security:spring-security-core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.springframework.security:spring-security-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.