OSSeva Blog
SecuritySpring Boot Vulnerabilities by Version: 12 CVEs in 2026, Lines 2.7 to 4.1
Spring Boot CVEs in 2026 and which versions fix them
spring.io published 12 CVEs against Spring Boot in 2026 (list checked 5 October 2026 and again on 17 November 2026, when spring.io's security page showed no advisory of any Spring project published after 20 August). Spring Boot 4.0.8, released on 20 August 2026, has the fix for all 12, 4.0.9 from 22 October 2026 carries it, and no 2026 CVE names 4.1. Spring Boot 3.5 left open source support on 30 June 2026, and the 2026 fixes for 3.4, 3.3 and 2.7 are Enterprise Support Only.
Running Spring Boot 2.x or Spring Framework 5? Spring Boot extended support for 2.x and Spring Framework 5 is the OSSeva page for those lines. Which JDK does each line need? Spring Boot 2.7 on Java 8 maps the pairs. Planning the move to 4? The Spring Boot 3.5 to 4 upgrade guide lists each breaking change and how to find it.
Running Spring Boot in production? OSSeva patches and supports it, end-of-life versions included.
Spring Boot extended support: what is coveredWhich Spring Boot lines still get fixes
Two Spring Boot lines have open source support. 4.1 is supported until 31 July 2027 and 4.0 until 31 December 2026; their latest releases are 4.1.2 and 4.0.9, both from 22 October 2026. Open source support for 3.5, the last 3.x line, ended on 30 June 2026 with 3.5.16, so every 3.x and 2.x release is now outside it. In 2026 spring.io has published 12 CVEs against Spring Boot itself. All 12 have public fixes on 4.0 and the ten that list 3.5 have public fixes there, but on 3.4, 3.3 and 2.7 every 2026 fix is marked Enterprise Support Only. The larger exposure is usually underneath Boot: the Spring Framework, Spring Security and Tomcat versions that each final release manages.
This guide covers Spring Boot's own CVEs and the dependency versions each Boot line pulls in. For the Framework CVEs in detail, see Spring Framework vulnerabilities by version.
Spring Boot release lines and their CVEs
Support dates are from spring.io, and the last public release is the newest version of each line on Maven Central. The CVE column lists Spring Boot advisories from 2023 onward whose affected ranges include the line.
| Line | Open source support | Last public release | Spring Boot CVEs that name it | Upstream fix on this line |
|---|---|---|---|---|
| 4.1 | Until 31 July 2027 | 4.1.2, 22 October 2026 | None so far | Not applicable |
| 4.0 | Until 31 December 2026 | 4.0.9, 22 October 2026 | All 12 from 2026 | 4.0.4, 4.0.6 and 4.0.7; 4.0.8 and 4.0.9 have all of them |
| 3.5 | Ended 30 June 2026 | 3.5.16, 25 June 2026 | 10 of the 2026 CVEs; not CVE-2026-40970 or CVE-2026-40976 | 3.5.12, 3.5.14 and 3.5.15; 3.5.16 has all of them |
| 3.4 | Ended 31 December 2025 | 3.4.13, 18 December 2025 | 9 of the 2026 CVEs, plus CVE-2025-22235 | 3.4.5 for CVE-2025-22235 only; the 2026 fixes are Enterprise Support Only |
| 3.3 | Ended 30 June 2025 | 3.3.13, 19 June 2025 | 7 of the 2026 CVEs, plus CVE-2025-22235 and CVE-2024-38807 | 3.3.3 and 3.3.11 for the 2024 and 2025 CVEs; no public 2026 fix |
| 3.2 | Ended 31 December 2024 | 3.2.12, 21 November 2024 | CVE-2025-22235, CVE-2024-38807; the 2026 advisories do not list 3.2 | 3.2.9 for CVE-2024-38807; no public fix for CVE-2025-22235 |
| 3.1 | Ended 30 June 2024 | 3.1.12, 23 May 2024 | CVE-2025-22235, CVE-2024-38807, CVE-2023-34055 | 3.1.6 for CVE-2023-34055 only |
| 3.0 | Ended 31 December 2023 | 3.0.13, 23 November 2023 | CVE-2024-38807, CVE-2023-34055, CVE-2023-20883, CVE-2023-20873 | 3.0.13 has the 2023 fixes; no public fix for CVE-2024-38807 |
| 2.7 | Ended 30 June 2023 | 2.7.18, 23 November 2023 | 7 of the 2026 CVEs, plus CVE-2025-22235, CVE-2024-38807 and the three 2023 CVEs | 2.7.18 has the 2023 fixes; nothing later is public |
| 2.6 and older | 2.6 ended 30 November 2022 | 2.6.15, 18 May 2023 | CVE-2023-20873 and CVE-2023-20883; 2026 ranges written as "2.7.x and earlier" include them | 2.6.15 and 2.5.15 for the 2023 CVEs only |
"Do not list" means the advisory leaves the line out. The 2026 advisories give ranges for 3.3 and 2.7 but skip 3.0 to 3.2, which is not a finding that those lines are safe. For dates on every line, see the Spring Boot end of life tracker.
Spring Boot's own CVEs
CVSS is NVD's own score where NVD has scored the record, otherwise the score from VMware as the CNA. For several 2026 records the two disagree widely, because NVD scored the missing hostname checks as network attacks while VMware scored them as needing an adjacent network and high complexity. None of these CVEs is in CISA's Known Exploited Vulnerabilities catalogue.
| CVE | Issue | CVSS | Public fix | Enterprise Support Only fix |
|---|---|---|---|---|
| CVE-2026-40976 | Default web security can be ineffective, leaving every endpoint open, when actuator auto-configuration is present without spring-boot-health | 9.1 (VMware) | 4.0.6 | None; only 4.0 is affected |
| CVE-2026-40974 | Cassandra auto-configuration skips hostname verification on SSL connections | 9.8 (NVD); 5.0 (VMware) | 4.0.6, 3.5.14 | 3.4.16, 3.3.19, 2.7.33 |
| CVE-2026-40971 | RabbitMQ auto-configuration with an SSL bundle skips hostname verification | 9.1 (NVD); 5.0 (VMware) | 4.0.6, 3.5.14 | None; 4.0 and 3.5 only |
| CVE-2026-22731 | Actuator authentication bypass for application endpoints under a health group's additional path | 8.1 (NVD) | 4.0.4, 3.5.12 | 3.4.15 |
| CVE-2026-22733 | Actuator authentication bypass for application endpoints under the Cloud Foundry actuator path | 8.1 (NVD) | 4.0.4, 3.5.12 | 3.4.15, 3.3.18, 2.7.32 |
| CVE-2026-40972 | Timing attack on the DevTools remote secret, which can end in uploading changed classes | 7.5 (VMware) | 4.0.6, 3.5.14 | 3.4.16, 3.3.19, 2.7.33 |
| CVE-2026-40975 | ${random.value} produces values that are not safe to use as secrets | 7.5 (NVD) | 4.0.6, 3.5.14 | 3.4.16, 3.3.19, 2.7.33 |
| CVE-2025-22235 | EndpointRequest.to() matches null/** when the referenced actuator endpoint is disabled or not exposed | 7.3 (VMware) | 3.4.5, 3.3.11 | 3.2.14, 3.1.16, 2.7.25 |
| CVE-2026-40973 | A local user who takes over the ApplicationTemp directory can read persisted sessions or plant a gadget chain | 7.0 (VMware) | 4.0.6, 3.5.14 | 3.4.16, 3.3.19, 2.7.33 |
| CVE-2026-40970 | Elasticsearch auto-configuration with an SSL bundle skips hostname verification | 6.8 (NVD) | 4.0.6 | None; only 4.0 is affected |
| CVE-2026-40977 | A local user with write access to the PID file location can corrupt a file on each start | 6.7 (NVD) | 4.0.6, 3.5.14 | 3.4.16, 3.3.19, 2.7.33 |
| CVE-2023-34055 | Crafted requests cause denial of service through server web observations when actuator is present | 6.5 (NVD) | 3.1.6, 3.0.13, 2.7.18 | None |
| CVE-2024-38807 | Custom signature verification of nested jars with spring-boot-loader can be fooled into trusting the wrong signer | 6.3 (VMware) | 3.3.3, 3.2.9 | 3.1.13, 3.0.17, 2.7.22 |
| CVE-2026-41001 | Embedded Artemis uses a fixed, predictable data directory a local user can pre-create | 5.3 (VMware) | 4.0.7, 3.5.15 | 4.0.6.1, 3.5.14.1, 3.4.17, 3.3.20, 2.7.34 |
| CVE-2026-40992 | Mail auto-configuration does not enable hostname verification | 5.0 (VMware) | 4.0.7, 3.5.15 | 4.0.6.1, 3.5.14.1, 3.4.17 |
| CVE-2023-20873 | Security bypass for applications deployed to Cloud Foundry | 9.8 (NVD) | 3.0.6, 2.7.11, 2.6.15, 2.5.15 | None |
Most of the list needs a specific setup, and each advisory spells it out. CVE-2026-40976 applies only to a servlet application with no Spring Security configuration of its own that depends on spring-boot-actuator-autoconfigure but not spring-boot-health. The two actuator bypasses need an application endpoint mapped under an actuator path, which the Spring team advises against. The hostname verification CVEs matter where a Boot application talks to Cassandra, RabbitMQ, Elasticsearch or a mail server over TLS on a network an attacker can reach. CVE-2026-40972 needs DevTools remote support, which should never run in production. The fifth 2023 CVE, CVE-2023-20883, is a denial of service through a reverse proxy cache, fixed in 3.0.7, 2.7.12, 2.6.15 and 2.5.15.
What each final release pulls in
A Spring Boot release fixes the versions of Spring Framework, Spring Security, Tomcat and hundreds of other libraries through spring-boot-dependencies. Leaving a Boot line usually means leaving those versions in place too. The versions below are from each release's POM on Maven Central.
| Boot release | Spring Framework | Spring Security | Tomcat | Notable fixes the managed versions lack |
|---|---|---|---|---|
| 4.1.2 | 7.0.10 | 7.1.2 | 11.0.27 | None of the fixes listed here; Tomcat releases after 11.0.27 (11.0.29 is on Maven Central). 4.1.1 managed Tomcat 11.0.24 and lacked the Tomcat fixes for CVE-2026-76183 |
| 4.0.9 | 7.0.10 | 7.0.8 | 11.0.27 | The same; 4.0.8 managed Tomcat 11.0.24 |
| 3.5.16 | 6.2.19 | 6.5.11 | 10.1.55 | Framework CVE-2026-59313, CVE-2026-47892 and CVE-2026-47884, all fixed in 6.2.20 for commercial customers only; Tomcat 10.1.56 onward, including CVE-2026-76183 |
| 3.4.13 | 6.2.15 | 6.4.13 | 10.1.50 | Framework 6.2.17 and 6.2.19, then the 6.2.20 fixes above; Tomcat 10.1.52 onward, including CVE-2026-43512 |
| 3.3.13 | 6.1.21 | 6.3.10 | 10.1.42 | Every Framework 6.1 fix from CVE-2025-41242 on, all commercial; Tomcat 10.1.43 onward, including CVE-2025-66614 |
| 3.2.12 | 6.1.15 | 6.2.8 | 10.1.33 | Framework CVE-2025-22233, public in 6.1.20, and everything after; Tomcat CVE-2025-24813 and later |
| 3.1.12 | 6.0.21 | 6.1.9 | 10.1.24 | Framework 6.0.23 and the commercial 6.0 fixes; Security CVE-2024-38821; Tomcat CVE-2025-24813 and later |
| 3.0.13 | 6.0.14 | 6.0.8 | 10.1.16 | The public Framework fixes up to 6.0.23, then commercial fixes; Security CVE-2024-38821; Tomcat CVE-2025-24813 and later |
| 2.7.18 | 5.3.31 | 5.7.11 | 9.0.83 | Framework 5.3.32 to 5.3.39 for the 2024 UriComponentsBuilder and ETag CVEs, then every commercial 5.3 fix, including CVE-2026-59313 and CVE-2026-47892; Security CVE-2024-38821; Tomcat CVE-2025-24813 and every 9.0 fix since 9.0.83 |
CVE-2026-59313 and CVE-2026-47892 carry a 9.8 CVSS 3.1 score from CISA-ADP. Both affect Framework 5.3.0 to 5.3.49, 6.0.0 to 6.0.30, 6.1.0 to 6.1.28, 6.2.0 to 6.2.19 and 7.0.0 to 7.0.8, so 4.0.8, 4.0.9, 4.1.1 and 4.1.2, on Framework 7.0.9 or 7.0.10, are the only current Boot releases with the fix. CVE-2024-38821, a 9.1 authorization bypass for static resources in WebFlux applications, was fixed publicly in Security 6.2.7 and 6.3.4 and in commercial releases for 6.1, 6.0, 5.8 and 5.7. CVE-2025-24813 is in CISA's catalogue, added on 1 April 2025, but it needs writes enabled on Tomcat's default servlet, which is off by default.
Tomcat is the one dependency you can fix yourself on every line, because Apache still supports 9.0, 10.1 and 11.0. Setting the tomcat.version property to 9.0.124 on Boot 2.7, 10.1.62 on 3.x or 11.0.29 on 4.x, the latest on Maven Central on 17 November 2026, takes the current Tomcat fixes without a new Boot release. Test it, since Boot was built against an older patch release. Framework and Security fixes cannot be taken that way on 2.7 to 3.5, because their open source releases stopped: the last public versions are 5.3.39, 6.0.23, 6.1.21 and 6.2.19 for Framework. Moving 2.7.18 from 5.3.31 to 5.3.39 still picks up the four public 2024 fixes. For the full Tomcat fix matrix, see Tomcat CVE fix releases for 9.0, 10.1 and 11.0.
What each line gets
Spring Boot 4.1 and 4.0
Both lines are supported, and 4.0.9 and 4.1.2 carry every Spring Boot fix above that applies to them. 4.0 has had all 12 of the 2026 CVEs, including CVE-2026-40976, which only affects 4.0, so an application on 4.0.0 to 4.0.5 should move to 4.0.9 now. Both releases manage Tomcat 11.0.27, which includes the Tomcat fix for CVE-2026-76183, scored 9.8 by CISA-ADP; the earlier 4.1.1 and 4.0.8 managed 11.0.24 and lacked it. Open source support for 4.0 ends on 31 December 2026. See Spring Boot 4.0 end of life.
Spring Boot 3.5
3.5.16 has every Spring Boot fix that lists 3.5, because the last 2026 advisory came out in June, before support ended. The gap is underneath: Framework 6.2.19 is exposed to CVE-2026-59313, CVE-2026-47892 and CVE-2026-47884, and the 6.2.20 release that fixes them is not on Maven Central. Commercial support for 3.5 is listed until 30 June 2032. See Spring Boot 3.5 end of life.
Spring Boot 3.0 to 3.4
3.4.13 and 3.3.13 have no public fix for any 2026 Spring Boot CVE that names them, including both actuator bypasses at 8.1. 3.0 to 3.2 are not listed in the 2026 advisories at all. 3.2.12 and 3.1.12 have no public fix for CVE-2025-22235, and 3.1.12 and 3.0.13 have none for CVE-2024-38807. All five final releases manage Framework and Security versions that are now patched only commercially. Moving from 3.x to 4.x brings Framework 7 and Jackson 3; see the Spring Boot migration guide.
Spring Boot 2.7 and older
2.7.18, from November 2023, is the last public 2.7 release, and Boot 2 runs on Framework 5.3 and Java 8, which is why so many applications are still there. Seven 2026 CVEs list 2.7, and spring.io's fixes for them are in 2.7.32, 2.7.33 and 2.7.34, all Enterprise Support Only. Spring.io lists commercial support for 2.7 until 30 June 2029. 2.6 and older stopped at 2.6.15 and 2.5.15 in May 2023. See Spring Boot 2 end of life and Spring Framework 5 end of life.
What to do on each line
- 4.0 and 4.1. Stay on the latest patch release, 4.1.2 or 4.0.9, which already manages Tomcat 11.0.27, and plan the move from 4.0 to 4.1 before 31 December 2026.
- 3.5. Set tomcat.version to 10.1.62. For Framework 6.2, check whether your application uses functional endpoints, Server-Sent Events or XsltView, which the 2026 Framework CVEs need, and plan the move to 4.x or take patched builds.
- 3.0 to 3.4. Upgrade to 3.5.16 as a stepping stone only if 4.x is close; otherwise move to 4.1 or take patched builds. Until then, keep application endpoints out of actuator paths, check that every EndpointRequest.to() target is enabled and exposed, and keep DevTools off production classpaths.
- 2.7 and older. Raise spring-framework.version to 5.3.39 and tomcat.version to 9.0.124 for the fixes that are still public, then plan the move to 3.x and 4.x or take patched builds. Enable hostname verification by hand where your version allows it, for example spring.mail.properties.mail.smtp.ssl.checkserveridentity=true.
For every Spring support date in one place, see the Spring support calendar.
Where OSSeva fits
OSSeva ships patched Spring Boot builds for 2.6.x, 2.7.x and 3.0.x to 3.5.x, and for 4.0.x after its open source end date. For Spring Boot 2.x the Spring Framework 5.3.x patches are included, and OSSeva backports fixes of this class to the end-of-life release lines it patches, delivered as signed artifacts through your own Maven or Gradle repository manager. They are available now on the Patch, Assure and Operate tiers. Assure adds a compliance attestation package and a Spring Boot 3 migration readiness assessment, and Operate adds 24/7 application monitoring with a 15-minute P1 response and a named senior Spring engineer. See Spring Boot extended support for the lines and projects covered, and Spring Boot versions for every line with its latest release and Java range.
Tags
Related articles
Spring Boot 2.7 on Java 8: what is still supported, and until when
November 15, 2026SecurityMySQL vulnerabilities by version: Oracle's 2026 advisories for 8.0, 8.4 and 9.7
November 17, 2026SecurityFinding embedded end-of-life Tomcat inside vendor appliances and applications
November 17, 2026SecurityNovember 2026 Patch Tuesday: the last .NET 8 and .NET 9 updates
November 11, 2026SecurityApache Storm Vulnerabilities by Version: CVEs for Storm 1.2, 2.x and 3.x
October 6, 2026Securityetcd Vulnerabilities by Version: CVEs for etcd 3.3, 3.4, 3.5, 3.6 and 3.7
October 6, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?