VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.springframework.cloud:spring-cloud-config-server: vulnerability history, versions and safety

org.springframework.cloud:spring-cloud-config-server is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 85 releases, from May 2019 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded C1 H3 M3
i
3 with no fix published

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

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

Most recent disclosure 07 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.springframework.cloud:spring-cloud-config-server vulnerabilities

Vulert verdict on org.springframework.cloud:spring-cloud-config-server 5.1.0-RC1 i

Updated on 22 Oct 2026

Careful: 5.1.0-RC1 has 3 known vulnerabilities, and 3 have 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 5.1.0-RC1 — affected i
  • Vulnerabilities on record 7 over 6 years · 4 in the last year i
  • Latest disclosure 07 May 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 3 i
  • Stars 2,050 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.cloud:spring-cloud-config-server, 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
5.0.6 22 Oct 2026 C1 H1 M1 Apache-2.0 No Details →
5.1.0-RC1 22 Oct 2026 C1 H1 M1 Apache-2.0 No Details →
5.1.0-M1 24 Sep 2026 C1 H1 M1 Apache-2.0 No Details →
5.0.5 20 Aug 2026 C1 H1 M1 Apache-2.0 No Details →
5.0.4 11 Jun 2026 C1 H1 M1 Apache-2.0 No Details →
4.3.4 11 Jun 2026 C1 H1 M1 Apache-2.0 No Details →
5.0.3 06 May 2026 C1 H1 M1 Apache-2.0 No Details →
4.3.3 06 May 2026 C1 H1 M1 Apache-2.0 No Details →
5.0.2 23 Mar 2026 C1 H1 M1 Apache-2.0 No Details →
4.3.2 23 Mar 2026 C1 H1 M1 Apache-2.0 No Details →
5.0.1 28 Jan 2026 C1 H1 M1 Apache-2.0 No Details →
4.3.1 16 Dec 2025 H1 Apache-2.0 Yes Details →
4.2.4 11 Dec 2025 C1 H1 M1 Apache-2.0 No Details →
5.0.0 24 Nov 2025 C1 H1 M1 Apache-2.0 No Details →
5.0.0-RC1 12 Nov 2025 C1 H1 M1 Apache-2.0 No Details →
5.0.0-M4 17 Oct 2025 C1 H1 M1 Apache-2.0 No Details →
5.0.0-M3 01 Oct 2025 C1 H1 M1 Apache-2.0 No Details →
5.0.0-M2 10 Sep 2025 C1 H1 M1 Apache-2.0 No Details →
5.0.0-M1 29 Jul 2025 C1 H1 M1 Apache-2.0 No Details →
4.2.3 09 Jul 2025 C1 H1 M1 Apache-2.0 No Details →
4.1.7 24 Jun 2025 C1 H1 M1 Apache-2.0 No Details →
4.3.0 29 May 2025 H1 Apache-2.0 Yes Details →
4.2.2 04 Apr 2025 C1 H1 M1 Apache-2.0 No Details →
4.1.6 04 Apr 2025 C1 H1 M1 Apache-2.0 No Details →
3.1.10 03 Apr 2025 C1 H1 M1 Apache-2.0 No Details →
4.2.1 18 Mar 2025 C1 H1 M1 Apache-2.0 No Details →
4.1.5 10 Jan 2025 C1 H1 M1 Apache-2.0 No Details →
4.2.0 03 Dec 2024 C1 H1 M1 Apache-2.0 No Details →
4.1.4 27 Nov 2024 C1 H1 M1 Apache-2.0 No Details →
4.1.3 10 Jul 2024 C1 H1 M1 Apache-2.0 No Details →
4.1.2 30 May 2024 C1 H1 M1 Apache-2.0 No Details →
4.1.1 27 Mar 2024 C1 H1 M1 Apache-2.0 No Details →
4.0.5 26 Jan 2024 C1 H1 M1 Apache-2.0 No Details →
3.1.9 18 Dec 2023 C1 H1 M1 Apache-2.0 No Details →
4.1.0 06 Dec 2023 C1 H1 M1 Apache-2.0 No Details →
4.0.4 27 Jul 2023 C1 H1 M1 Apache-2.0 No Details →
3.1.8 29 Jun 2023 C1 H1 M1 Apache-2.0 No Details →
4.0.3 24 May 2023 C1 H1 M1 Apache-2.0 No Details →
3.1.7 27 Apr 2023 C1 H1 M1 Apache-2.0 No Details →
4.0.2 28 Mar 2023 C1 H1 M1 Apache-2.0 No Details →
3.1.6 23 Feb 2023 C1 H1 M1 Apache-2.0 No Details →
4.0.1 25 Jan 2023 C1 H1 M1 Apache-2.0 No Details →
4.0.0 15 Dec 2022 C1 H1 M1 Apache-2.0 No Details →
3.1.5 03 Nov 2022 C1 H1 M1 Apache-2.0 No Details →
3.1.4 06 Sep 2022 C1 H1 M1 Apache-2.0 No Details →
3.0.7 29 Jun 2022 none Apache-2.0 — Details →
3.1.3 26 May 2022 C1 H1 M1 Apache-2.0 No Details →
3.1.2 27 Apr 2022 C1 H1 M1 Apache-2.0 No Details →
3.1.1 17 Feb 2022 C1 H1 M1 Apache-2.0 No Details →
3.0.6 15 Dec 2021 none Apache-2.0 — Details →
3.1.0 01 Dec 2021 C1 H1 M1 Apache-2.0 No Details →
3.0.5 21 Sep 2021 none Apache-2.0 — Details →
3.0.4 27 May 2021 none Apache-2.0 — Details →
2.2.8.RELEASE 21 Apr 2021 none Apache-2.0 — Details →
3.0.3 17 Mar 2021 none Apache-2.0 — Details →
2.2.7.RELEASE 11 Feb 2021 none Apache-2.0 — Details →
3.0.2 27 Jan 2021 none Apache-2.0 — Details →
3.0.1 08 Jan 2021 none Apache-2.0 — Details →
3.0.0 21 Dec 2020 none Apache-2.0 — Details →
2.2.6.RELEASE 09 Nov 2020 none Apache-2.0 — Details →
2.2.5.RELEASE 28 Aug 2020 none Apache-2.0 — Details →
2.2.4.RELEASE 31 Jul 2020 none Apache-2.0 — Details →
2.2.3.RELEASE 28 May 2020 none Apache-2.0 — Details →
2.1.9.RELEASE 28 May 2020 H1 Apache-2.0 Yes Details →
2.1.8.RELEASE 15 May 2020 H1 Apache-2.0 Yes Details →
2.2.2.RELEASE 04 Mar 2020 none Apache-2.0 — Details →
2.1.7.RELEASE 02 Mar 2020 H1 Apache-2.0 Yes Details →
2.1.6.RELEASE 31 Jan 2020 H1 M1 Apache-2.0 Yes Details →
2.2.1.RELEASE 20 Dec 2019 none Apache-2.0 — Details →
2.2.0.RELEASE 26 Nov 2019 none Apache-2.0 — Details →
2.1.5.RELEASE 18 Nov 2019 H1 M1 Apache-2.0 Yes Details →
2.1.4.RELEASE 09 Sep 2019 H1 M1 Apache-2.0 Yes Details →
2.1.3.RELEASE 20 Jun 2019 H1 M1 Apache-2.0 Yes Details →
2.0.5.RELEASE 07 Jun 2019 none Apache-2.0 — Details →
1.4.7.RELEASE 22 May 2019 none Apache-2.0 — Details →
2.1.2.RELEASE 16 Apr 2019 H1 M1 Apache-2.0 Yes Details →
2.0.4.RELEASE 16 Apr 2019 none Apache-2.0 — Details →
1.4.6.RELEASE 16 Apr 2019 M1 Apache-2.0 Yes Details →
2.1.1.RELEASE 05 Mar 2019 H1 M1 Apache-2.0 Yes Details →
2.0.3.RELEASE 22 Feb 2019 none Apache-2.0 — Details →
2.1.0.RELEASE 22 Jan 2019 H1 M1 Apache-2.0 Yes Details →
2.0.2.RELEASE 23 Oct 2018 none Apache-2.0 — Details →
1.4.5.RELEASE 15 Oct 2018 M1 Apache-2.0 Yes Details →
2.0.1.RELEASE 31 Jul 2018 none Apache-2.0 — Details →
1.4.4.RELEASE 28 Jun 2018 M1 Apache-2.0 Yes Details →
2.0.0.RELEASE 18 Jun 2018 none Apache-2.0 — Details →
1.4.3.RELEASE 26 Mar 2018 M1 Apache-2.0 Yes Details →
1.4.2.RELEASE 08 Feb 2018 M1 Apache-2.0 Yes Details →
1.4.1.RELEASE 12 Jan 2018 M1 Apache-2.0 Yes Details →
1.3.4.RELEASE 21 Dec 2017 M1 Apache-2.0 Yes Details →
1.4.0.RELEASE 20 Nov 2017 M1 Apache-2.0 Yes Details →
1.3.3.RELEASE 02 Oct 2017 M1 Apache-2.0 Yes Details →
1.3.2.RELEASE 20 Jul 2017 M1 Apache-2.0 Yes Details →
1.3.1.RELEASE 19 May 2017 M1 Apache-2.0 Yes Details →
1.3.0.RELEASE 07 Apr 2017 M1 Apache-2.0 Yes Details →
1.2.3.RELEASE 08 Mar 2017 M1 Apache-2.0 Yes Details →
1.2.2.RELEASE 23 Nov 2016 M1 Apache-2.0 Yes Details →
1.2.1.RELEASE 18 Oct 2016 M1 Apache-2.0 Yes Details →
1.2.0.RELEASE 22 Sep 2016 M1 Apache-2.0 Yes Details →
1.2.0.M1 22 Aug 2016 M1 Apache-2.0 Yes Details →
1.1.3.RELEASE 18 Aug 2016 M1 — Yes Details →
1.1.2.RELEASE 30 Jun 2016 M1 — Yes Details →
1.1.1.RELEASE 07 Jun 2016 M1 — Yes Details →
1.1.0.RELEASE 10 May 2016 M1 — Yes Details →
1.0.4.RELEASE 25 Jan 2016 M1 — Yes Details →
1.0.3.RELEASE 24 Nov 2015 M1 — Yes Details →
1.0.2.RELEASE 25 Jun 2015 M1 — Yes Details →
1.0.1.RELEASE 24 Apr 2015 M1 — Yes Details →
1.0.0.RELEASE 03 Mar 2015 M1 — Yes Details →

All 109 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
  • 2020 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for org.springframework.cloud:spring-cloud-config-server

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-40982: Spring Cloud Config Path Traversal Vulnerability 9.1 critical No fix published 07 May 2026
CVE-2026-22739: Spring Cloud Config Server Path Traversal Vulnerability Allows Arbitrary File Access 8.6 high 4.3.2 24 Mar 2026
CVE-2020-5410: Directory Traversal Attack in Spring Cloud Config 7.5 high 2.1.9 05 Jun 2020
CVE-2026-41002: Spring Cloud Config Server Vulnerable to TOCTOU Attack 7.2 high No fix published 07 May 2026
CVE-2019-3799: Path Traversal in Spring Cloud Config 6.5 medium 1.4.6 23 May 2019

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.cloud:spring-cloud-config-server

Is org.springframework.cloud:spring-cloud-config-server safe to use?

Vulert records 7 vulnerabilities for org.springframework.cloud:spring-cloud-config-server in Maven: 1 critical, 3 high, 3 medium and 0 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is org.springframework.cloud:spring-cloud-config-server's Vulert package health score?

Vulert scores org.springframework.cloud:spring-cloud-config-server 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.cloud:spring-cloud-config-server affected?

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

How many vulnerabilities does org.springframework.cloud:spring-cloud-config-server have?

7 vulnerabilities are recorded for org.springframework.cloud:spring-cloud-config-server in the Maven ecosystem: 1 critical, 3 high, 3 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.springframework.cloud:spring-cloud-config-server vulnerabilities disclosed?

4 vulnerabilities were recorded for org.springframework.cloud:spring-cloud-config-server in the last 12 months, and the oldest entry in this database dates to 23 May 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.cloud:spring-cloud-config-server 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.cloud:spring-cloud-config-server for upcoming vulnerabilities?

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