Vulnerability Database · Maven · Package report

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

Q: How do I monitor org.springframework.cloud:spring-cloud-commons for upcoming vulnerabilities?

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

org.springframework.cloud:spring-cloud-commons is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.springframework.cloud:spring-cloud-commons vulnerabilities

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

Updated on 23 Oct 2026

Good news: 5.1.0-RC1, the version you would install today, has no known vulnerabilities.

Package health score 85/100

Security Minor issues
Maintenance Sustainable
Popularity Widely used
Community Moderate

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

Current release 5.1.0-RC1 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 751 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for org.springframework.cloud:spring-cloud-commons, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
5.0.4	23 Oct 2026	none	Apache-2.0	—	Details →
5.1.0-RC1	23 Oct 2026	none	Apache-2.0	—	Details →
5.1.0-M1	24 Sep 2026	none	Apache-2.0	—	Details →
5.0.3	20 Aug 2026	none	Apache-2.0	—	Details →
5.0.2	11 Jun 2026	none	Apache-2.0	—	Details →
4.3.3	11 Jun 2026	none	Apache-2.0	—	Details →
4.3.2	01 Apr 2026	none	Apache-2.0	—	Details →
5.0.1	28 Jan 2026	none	Apache-2.0	—	Details →
4.3.1	16 Dec 2025	none	Apache-2.0	—	Details →
4.2.4	11 Dec 2025	none	Apache-2.0	—	Details →
5.0.0	24 Nov 2025	none	Apache-2.0	—	Details →
5.0.0-RC1	12 Nov 2025	none	Apache-2.0	—	Details →
4.2.3	23 Oct 2025	none	Apache-2.0	—	Details →
5.0.0-M4	17 Oct 2025	none	Apache-2.0	—	Details →
5.0.0-M3	01 Oct 2025	none	Apache-2.0	—	Details →
5.0.0-M2	10 Sep 2025	none	Apache-2.0	—	Details →
5.0.0-M1	29 Jul 2025	none	Apache-2.0	—	Details →
4.2.2	09 Jul 2025	none	Apache-2.0	—	Details →
4.1.6	21 Jun 2025	none	Apache-2.0	—	Details →
4.3.0	29 May 2025	none	Apache-2.0	—	Details →
4.2.1	18 Mar 2025	none	Apache-2.0	—	Details →
4.2.0	03 Dec 2024	none	Apache-2.0	—	Details →
4.1.5	27 Nov 2024	none	Apache-2.0	—	Details →
3.1.9	19 Sep 2024	none	Apache-2.0	—	Details →
4.1.4	10 Jul 2024	none	Apache-2.0	—	Details →
4.1.3	30 May 2024	none	Apache-2.0	—	Details →
4.1.2	27 Mar 2024	none	Apache-2.0	—	Details →
4.0.5	26 Jan 2024	none	Apache-2.0	—	Details →
4.1.1	23 Jan 2024	none	Apache-2.0	—	Details →
3.1.8	18 Dec 2023	none	Apache-2.0	—	Details →
4.1.0	06 Dec 2023	none	Apache-2.0	—	Details →
4.0.4	27 Jul 2023	none	Apache-2.0	—	Details →
3.1.7	29 Jun 2023	none	Apache-2.0	—	Details →
4.0.3	24 May 2023	none	Apache-2.0	—	Details →
4.0.2	28 Mar 2023	none	Apache-2.0	—	Details →
3.1.6	23 Feb 2023	none	Apache-2.0	—	Details →
4.0.1	25 Jan 2023	none	Apache-2.0	—	Details →
4.0.0	15 Dec 2022	none	Apache-2.0	—	Details →
3.1.5	03 Nov 2022	none	Apache-2.0	—	Details →
3.1.4	06 Sep 2022	none	Apache-2.0	—	Details →
3.0.6	29 Jun 2022	none	Apache-2.0	—	Details →
3.1.3	26 May 2022	none	Apache-2.0	—	Details →
3.1.2	27 Apr 2022	none	Apache-2.0	—	Details →
3.1.1	17 Feb 2022	none	Apache-2.0	—	Details →
3.0.5	15 Dec 2021	none	Apache-2.0	—	Details →
3.1.0	01 Dec 2021	none	Apache-2.0	—	Details →
3.0.4	21 Sep 2021	none	Apache-2.0	—	Details →
2.2.9.RELEASE	07 Jul 2021	none	Apache-2.0	—	Details →
3.0.3	27 May 2021	none	Apache-2.0	—	Details →
2.2.8.RELEASE	21 Apr 2021	none	Apache-2.0	—	Details →
3.0.2	17 Mar 2021	none	Apache-2.0	—	Details →
2.2.7.RELEASE	11 Feb 2021	none	Apache-2.0	—	Details →
3.0.1	27 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.6.RELEASE	15 May 2020	none	Apache-2.0	—	Details →
2.2.2.RELEASE	04 Mar 2020	none	Apache-2.0	—	Details →
2.1.5.RELEASE	31 Jan 2020	none	Apache-2.0	—	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.4.RELEASE	18 Nov 2019	none	Apache-2.0	—	Details →
2.1.3.RELEASE	09 Sep 2019	none	Apache-2.0	—	Details →
2.1.2.RELEASE	20 Jun 2019	none	Apache-2.0	—	Details →
2.0.4.RELEASE	07 Jun 2019	none	Apache-2.0	—	Details →
1.3.6.RELEASE	22 May 2019	none	Apache-2.0	—	Details →
2.1.1.RELEASE	05 Mar 2019	none	Apache-2.0	—	Details →
2.0.3.RELEASE	22 Feb 2019	none	Apache-2.0	—	Details →
2.1.0.RELEASE	22 Jan 2019	none	Apache-2.0	—	Details →
2.0.2.RELEASE	23 Oct 2018	none	Apache-2.0	—	Details →
1.3.5.RELEASE	15 Oct 2018	none	Apache-2.0	—	Details →
2.0.1.RELEASE	31 Jul 2018	none	Apache-2.0	—	Details →
1.3.4.RELEASE	28 Jun 2018	none	Apache-2.0	—	Details →
2.0.0.RELEASE	18 Jun 2018	none	Apache-2.0	—	Details →
1.3.3.RELEASE	26 Mar 2018	none	Apache-2.0	—	Details →
1.3.2.RELEASE	08 Feb 2018	none	Apache-2.0	—	Details →
1.3.1.RELEASE	11 Jan 2018	none	Apache-2.0	—	Details →
1.2.5.RELEASE	21 Dec 2017	none	Apache-2.0	—	Details →
1.3.0.RELEASE	20 Nov 2017	none	Apache-2.0	—	Details →
1.2.4.RELEASE	02 Oct 2017	none	Apache-2.0	—	Details →
1.2.3.RELEASE	12 Jul 2017	none	Apache-2.0	—	Details →
1.2.2.RELEASE	19 May 2017	none	Apache-2.0	—	Details →
1.2.1.RELEASE	12 May 2017	none	Apache-2.0	—	Details →
1.1.9.RELEASE	02 May 2017	none	Apache-2.0	—	Details →
1.2.0.RELEASE	05 Apr 2017	none	Apache-2.0	—	Details →
1.1.8.RELEASE	07 Mar 2017	none	Apache-2.0	—	Details →
1.1.7.RELEASE	09 Jan 2017	none	Apache-2.0	—	Details →
1.1.6.RELEASE	23 Nov 2016	none	Apache-2.0	—	Details →
1.1.5.RELEASE	01 Nov 2016	none	Apache-2.0	—	Details →
1.1.4.RELEASE	17 Oct 2016	none	Apache-2.0	—	Details →
1.1.3.RELEASE	21 Sep 2016	none	Apache-2.0	—	Details →
1.1.2.RELEASE	06 Sep 2016	none	Apache-2.0	—	Details →
1.1.1.RELEASE	06 Jun 2016	none	Apache-2.0	—	Details →
1.1.0.RELEASE	09 May 2016	none	Apache-2.0	—	Details →
1.0.5.RELEASE	27 Jan 2016	none	Apache-2.0	—	Details →
1.0.4.RELEASE	25 Jan 2016	none	Apache-2.0	—	Details →
1.0.3.RELEASE	24 Nov 2015	none	Apache-2.0	—	Details →
1.0.2.RELEASE	25 Jun 2015	none	Apache-2.0	—	Details →
1.0.1.RELEASE	24 Apr 2015	none	—	—	Details →
1.0.0.RELEASE	03 Mar 2015	none	—	—	Details →

All 102 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for org.springframework.cloud:spring-cloud-commons

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.springframework.cloud:spring-cloud-commons

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

Vulert has no vulnerabilities on record for org.springframework.cloud:spring-cloud-commons 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.springframework.cloud:spring-cloud-commons's Vulert package health score?

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

No. 5.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.cloud:spring-cloud-commons have?

0 vulnerabilities are recorded for org.springframework.cloud:spring-cloud-commons 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.springframework.cloud:spring-cloud-commons vulnerabilities disclosed?

0 vulnerabilities were recorded for org.springframework.cloud:spring-cloud-commons 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.springframework.cloud:spring-cloud-commons 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-commons 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-commons version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.