Vulnerability Database · Maven · Package report

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

org.springframework.cloud:spring-cloud-gateway is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 67 releases, from Nov 2021 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
3 vulnerabilities recorded C1 H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 10 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.springframework.cloud:spring-cloud-gateway 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. Older releases do — the table below lists all 3.

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • 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 3 over 4 years · 1 in the last year i
  • Latest disclosure 10 Apr 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Stars 4,915 i
  • OpenSSF scorecard 4/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-gateway, 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.4 22 Oct 2026 none Apache-2.0 — Details →
5.1.0-RC1 22 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.5 11 Jun 2026 none Apache-2.0 — Details →
4.3.4 01 Apr 2026 none Apache-2.0 — Details →
5.0.1 28 Jan 2026 none Apache-2.0 — Details →
4.3.3 16 Dec 2025 none Apache-2.0 — Details →
4.2.7 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 →
5.0.0-M4 17 Oct 2025 none Apache-2.0 — Details →
4.3.2 15 Oct 2025 none Apache-2.0 — Details →
4.2.6 15 Oct 2025 none Apache-2.0 — Details →
5.0.0-M3 01 Oct 2025 none Apache-2.0 — Details →
5.0.0-M2 11 Sep 2025 none Apache-2.0 — Details →
4.3.1 08 Sep 2025 none Apache-2.0 — Details →
4.2.5 08 Sep 2025 none Apache-2.0 — Details →
5.0.0-M1 29 Jul 2025 none Apache-2.0 — Details →
4.2.4 10 Jul 2025 none Apache-2.0 — Details →
4.1.9 24 Jun 2025 H1 Apache-2.0 Yes Details →
4.3.0 29 May 2025 none Apache-2.0 — Details →
4.2.3 28 May 2025 none Apache-2.0 — Details →
4.1.8 28 May 2025 H1 Apache-2.0 Yes Details →
3.1.10 28 May 2025 H1 Apache-2.0 Yes Details →
4.2.2 03 Apr 2025 none Apache-2.0 — Details →
4.1.7 03 Apr 2025 H1 Apache-2.0 Yes Details →
4.2.1 18 Mar 2025 none Apache-2.0 — Details →
4.2.0 03 Dec 2024 H1 Apache-2.0 Yes Details →
4.1.6 26 Nov 2024 H1 Apache-2.0 Yes Details →
4.1.5 10 Jul 2024 H1 Apache-2.0 Yes Details →
4.1.4 30 May 2024 H1 Apache-2.0 Yes Details →
4.1.3 17 Apr 2024 H1 Apache-2.0 Yes Details →
4.1.2 27 Mar 2024 H1 Apache-2.0 Yes Details →
4.0.9 26 Jan 2024 H1 Apache-2.0 Yes Details →
4.1.1 22 Dec 2023 H1 Apache-2.0 Yes Details →
4.1.0 06 Dec 2023 H1 Apache-2.0 Yes Details →
3.1.9 03 Nov 2023 H1 Apache-2.0 Yes Details →
4.0.8 03 Nov 2023 H1 Apache-2.0 Yes Details →
4.0.7 27 Jul 2023 H1 Apache-2.0 Yes Details →
3.1.8 29 Jun 2023 H1 Apache-2.0 Yes Details →
4.0.6 24 May 2023 H1 Apache-2.0 Yes Details →
4.0.5 02 May 2023 H1 Apache-2.0 Yes Details →
3.1.7 27 Apr 2023 H1 Apache-2.0 Yes Details →
4.0.4 28 Mar 2023 H1 Apache-2.0 Yes Details →
4.0.3 24 Feb 2023 H1 Apache-2.0 Yes Details →
3.1.6 24 Feb 2023 H1 Apache-2.0 Yes Details →
4.0.2 21 Feb 2023 H1 Apache-2.0 Yes Details →
3.1.5 27 Jan 2023 H1 Apache-2.0 Yes Details →
4.0.1 25 Jan 2023 H1 Apache-2.0 Yes Details →
4.0.0 15 Dec 2022 H1 Apache-2.0 Yes Details →
3.1.4 06 Sep 2022 H1 Apache-2.0 Yes Details →
3.0.8 29 Jun 2022 H1 Apache-2.0 Yes Details →
3.1.3 26 May 2022 H1 Apache-2.0 Yes Details →
3.1.2 27 Apr 2022 H1 Apache-2.0 Yes Details →
3.0.7 17 Feb 2022 H1 Apache-2.0 Yes Details →
3.1.1 17 Feb 2022 H1 Apache-2.0 Yes Details →
3.0.6 15 Dec 2021 C1 H1 Apache-2.0 Yes Details →
3.1.0 01 Dec 2021 H1 Apache-2.0 Yes Details →
3.0.5 03 Nov 2021 C1 H1 Apache-2.0 Yes Details →
2.2.10.RELEASE 03 Nov 2021 C1 H1 Apache-2.0 Yes Details →
3.0.4 22 Sep 2021 C1 H1 M1 Apache-2.0 Yes Details →
2.2.9.RELEASE 06 Jul 2021 C1 H1 Apache-2.0 Yes Details →
3.0.3 28 May 2021 C1 H1 M1 Apache-2.0 Yes Details →
2.2.8.RELEASE 21 Apr 2021 C1 H1 Apache-2.0 Yes Details →
3.0.2 17 Mar 2021 C1 H1 M1 Apache-2.0 Yes Details →
2.2.7.RELEASE 11 Feb 2021 C1 H1 Apache-2.0 Yes Details →
3.0.1 27 Jan 2021 C1 H1 M1 Apache-2.0 Yes Details →
3.0.0 21 Dec 2020 C1 H1 M1 Apache-2.0 Yes Details →
2.2.6.RELEASE 09 Nov 2020 C1 H1 Apache-2.0 Yes Details →
2.2.5.RELEASE 28 Aug 2020 C1 H1 Apache-2.0 Yes Details →
2.2.4.RELEASE 31 Jul 2020 C1 H1 Apache-2.0 Yes Details →
2.2.3.RELEASE 28 May 2020 C1 H1 Apache-2.0 Yes Details →
2.2.2.RELEASE 04 Mar 2020 C1 H1 Apache-2.0 Yes Details →
2.1.5.RELEASE 31 Jan 2020 C1 H1 Apache-2.0 Yes Details →
2.2.1.RELEASE 20 Dec 2019 C1 H1 Apache-2.0 Yes Details →
2.2.0.RELEASE 26 Nov 2019 C1 H1 Apache-2.0 Yes Details →
2.1.4.RELEASE 18 Nov 2019 C1 H1 Apache-2.0 Yes Details →
2.1.3.RELEASE 09 Sep 2019 C1 H1 Apache-2.0 Yes Details →
2.1.2.RELEASE 20 Jun 2019 C1 H1 Apache-2.0 Yes Details →
2.0.4.RELEASE 08 Jun 2019 C1 H1 Apache-2.0 Yes Details →
1.0.3.RELEASE 22 May 2019 C1 H1 Apache-2.0 Yes Details →
2.1.1.RELEASE 05 Mar 2019 C1 H1 Apache-2.0 Yes Details →
2.0.3.RELEASE 22 Feb 2019 C1 H1 Apache-2.0 Yes Details →
2.1.0.RELEASE 22 Jan 2019 C1 H1 Apache-2.0 Yes Details →
2.0.2.RELEASE 23 Oct 2018 C1 H1 Apache-2.0 Yes Details →
2.0.1.RELEASE 31 Jul 2018 C1 H1 Apache-2.0 Yes Details →
1.0.2.RELEASE 29 Jun 2018 C1 H1 Apache-2.0 Yes Details →
2.0.0.RELEASE 19 Jun 2018 C1 H1 Apache-2.0 Yes Details →
1.0.1.RELEASE 12 Jan 2018 C1 H1 Apache-2.0 Yes Details →
1.0.0.RELEASE 22 Nov 2017 C1 H1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2026 1

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

03 Vulnerabilities

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

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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.cloud:spring-cloud-gateway

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

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

Vulert scores org.springframework.cloud:spring-cloud-gateway 79/100, which reads as in good shape. 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-gateway 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-gateway have?

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

1 vulnerability was recorded for org.springframework.cloud:spring-cloud-gateway in the last 12 months, and the oldest entry in this database dates to 10 Nov 2021. 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-gateway 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-gateway 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-gateway version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.