Spring Boot vulnerabilitiesRanked by how likely they are to be used.

Product196 versions
The short answer

Spring Boot is made by VMware. We track 9 published vulnerabilities listed under that exact name, across 196 versions. None of them is on the list of flaws known to be exploited today. VMware lists newer releases under their own names, such as Spring Boot Tools, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Spring Boot listed under other names? Yes.

VMware also lists Spring Boot under more specific names, such as Spring Boot Tools. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Spring Boot vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Spring Boot's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Spring Boot flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 2.4%

    Element Plug-in for vCenter Server incorporates SpringBoot Framework.

    CVSS9.8Published15 Mar 2021
  2. 1.6%

    When using Apache Shiro before 1.11.0 together with Spring Boot 2.6+, a specially crafted HTTP request may cause an authentication bypass.

    CVSS7.5Published14 Jan 2023
  3. 1.2%

    In Spring Boot versions 2.7.0 - 2.7.17, 3.0.0-3.0.12 and 3.1.0-3.1.5, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition.

    CVSS5.3Published28 Nov 2023
  4. 1.2%

    Spring Boot supports an embedded launch script that can be used to easily run the application as a systemd or init.d linux service.

    CVSS5.9Published19 Mar 2018
  5. 1.1%

    In Spring Boot versions 3.0.0 - 3.0.5, 2.7.0 - 2.7.10, and older unsupported versions, an application that is deployed to Cloud Foundry could be susceptible to a security bypass.

    CVSS9.8Published20 Apr 2023
  6. 1.0%

    An issue in Dromara SaToken version 1.36.0 and before allows a remote attacker to escalate privileges via a crafted payload to the URL.

    CVSS9.8Published25 Oct 2023
  7. 0.9%

    In Spring Boot versions 3.0.0 - 3.0.6, 2.7.0 - 2.7.11, 2.6.0 - 2.6.14, 2.5.0 - 2.5.14 and older unsupported versions, there is potential for a denial-of-service (DoS) attack if Spring MVC is used together with a...

    CVSS7.5Published26 May 2023
  8. 0.6%

    spring-boot versions prior to version v2.2.11.RELEASE was vulnerable to temporary directory hijacking.

    CVSS7.8Published30 Mar 2022
Precursor Intelligence

Running Spring Boot? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 9 published vulnerabilities listed under the name Spring Boot, across 196 versions.

None of Spring Boot's vulnerabilities is on the list of flaws known to be exploited today.

VMware also lists Spring Boot under more specific names, such as Spring Boot Tools. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Spring Boot. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.