Back to blog

OSSeva Blog

Operations

Spring Boot 4.0 End of Support Checklist: 12 Steps Before 31 December 2026

9 min read

The short answer

Spring Boot 4.0 reaches the end of open source support on 31 December 2026, and Broadcom's commercial support for it runs to 31 December 2027. The latest 4.0 release is 4.0.9, from 22 October 2026. To prepare: find every 4.0 application, take 4.0.9 now, choose 4.1 or 4.2 as the target, clear what 4.1 removes, rehearse and decide cover for anything that cannot move.

Spring Security 7.0, which Boot 4.0 manages, ends open source support on the same day. Spring Framework 7.0, underneath both, is supported in open source to 31 July 2027, so the move to Boot 4.1 changes Security and the managed libraries but not the core framework generation. This checklist covers the application work; Spring Boot 4.0 end of life and Spring Security 7.0 end of life carry the dates and the advisories.

Running Spring Framework in production? OSSeva patches and supports it, end-of-life versions included.

Spring Framework extended support: what is covered

Which end dates apply to Spring Boot 4.0?

LineOpen source support endsCommercial support endsLatest release (13 Nov 2026)
Spring Boot 4.0.x31 Dec 202631 Dec 20274.0.9 (22 Oct 2026)
Spring Security 7.0.x (managed by 4.0)31 Dec 202631 Dec 20277.0.8
Spring Framework 7.0.x (managed by 4.0 and 4.1)31 Jul 202731 Jul 20287.0.10 (managed by 4.0.9)
Spring Boot 4.1.x31 Jul 202731 Jul 20284.1.2
Spring Boot 4.2.x31 Dec 202731 Dec 20284.2.0-RC2 on Maven Central; spring.io lists a November 2026 release

Sources: the support tab on spring.io for Spring Boot and Spring Security and the generations data behind it (api.spring.io), checked 13 November 2026. The tab shows months, and the data gives the day. Commercial support means Broadcom's paid Spring releases; the policy page says the tab "does not define the enterprise support policy", so check your own contract.

Phase 1: Find and inspect

Step 1. List every Spring Boot 4.0 application

Search source, builds and running systems. A Boot jar records its version in the manifest.

grep -rn --include=pom.xml -A2 "spring-boot-starter-parent" . | grep -E "<version>4\.0\."
grep -rnE --include="build.gradle*" --include="settings.gradle*" --include="*.toml" "org.springframework.boot.*4\.0\." .
unzip -p app.jar META-INF/MANIFEST.MF | grep -i "Spring-Boot-Version"
kubectl get pods -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"/"}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}'

Check the applications nobody lists: services built from a template that pinned 4.0 when it was new, internal tools, and vendor products that embed Boot. Note the owner, the environment and whether each faces the internet.

Step 2. Record what 4.0 manages in each one

mvn -q dependency:tree -Dincludes=org.springframework,org.apache.tomcat.embed,tools.jackson.core
./gradlew dependencies --configuration runtimeClasspath | grep -E "springframework|tomcat-embed|jackson"

Spring Boot 4.0.9 manages Spring Framework 7.0.10, Spring Security 7.0.8, Tomcat 11.0.27, Hibernate 7.2.25.Final and Jackson 3.1.7, with Jackson 2.21.7 managed alongside it. Boot 4.1.2 manages the same Framework and Tomcat, with Spring Security 7.1.2 and Hibernate 7.4.13.Final. Those figures come from the published dependency versions of each release. List any versions you override, because they sit outside the managed set.

Step 3. Take 4.0.9 now, whatever the longer plan is

Two Boot advisories published in April 2026 hit 4.0.0 to 4.0.5 and are fixed in 4.0.6: CVE-2026-40976, where default web security could be ineffective in some Actuator setups, and CVE-2026-40971, missing hostname verification in RabbitMQ SSL bundle connections. Spring Framework 7.0.8 and earlier are affected by CVE-2026-59313, fixed in 7.0.9 in open source. Anything on a 4.0 release older than 4.0.9 should move to it this week, because the 4.0 line only ships open source fixes until 31 December.

Step 4. Check Spring Security 7.0 separately

Authentication is the worst place to carry open advisories. CVE-2026-59270, the embedded UnboundID LDAP server exposing a well-known administrative bind DN on all interfaces, affects Spring Security 7.0.0 to 7.0.6 and is fixed in 7.0.7 and 7.1.1 in open source. CVE-2026-22732, where HTTP headers may not be written, affects 7.0.0 to 7.0.3 and is fixed in 7.0.4. Check the version each application actually resolves, and whether it uses the features the advisories name.

Phase 2: Choose the path

Step 5. Pick the target for each application

TargetOpen source support endsWhat changesUse it when
Spring Boot 4.131 Jul 2027Same Spring Framework 7.0. Spring Security moves from 7.0 to 7.1. 4.0 deprecations are removed.You want a supported line now. The default choice.
Spring Boot 4.231 Dec 2027A new minor; only release candidates were on Maven Central on 13 November 2026.You can wait for general availability and want the longest runway.
Stay on 4.0.9 with coverEnds 31 Dec 2026Nothing changes in the code.The application cannot be retested before the date. See step 11.

A team that moves to 4.1 now has until 31 July 2027 before the same decision returns, so plan the next move while you do this one.

Step 6. Read what Boot 4.1 removes

The 4.1 release notes say that classes, methods and properties deprecated in 4.0 have been removed. They also list: Derby support deprecated, with H2 or HSQL suggested; the layertools jar mode removed in favour of tools; -DskipTests no longer skipping AOT processing of tests, with only maven.test.skip honoured; a stricter spring.data.jpa.repositories.bootstrap-mode; a Tomcat temporary directory that is now cleaned up when the context closes; and a supported jOOQ of 3.20, which needs Java 21 or later. Search your code and build for each one.

grep -rnE "layertools|derby|bootstrap-mode|skipTests" --include=pom.xml --include="*.gradle*" --include="*.properties" --include="*.yml" --include="Dockerfile*" .

Phase 3: Rehearse and protect

Step 7. Build with deprecation warnings on 4.0.9

Everything deprecated in 4.0 is removed in 4.1, so clear the warnings on 4.0.9 first. That keeps the version change itself small.

mvn -Dmaven.compiler.showDeprecation=true -Dmaven.compiler.showWarnings=true clean verify
./gradlew clean build --warning-mode=all

Step 8. Check the container, the JDK and the build tool

Boot 4 supports Java 17 and later, up to Java 27 in the 4.0.9 documentation, with Maven 3.6.3 or later and Gradle 8.14 or later or Gradle 9, and Tomcat 11.0.x or Jetty 12.1.x on a Servlet 6.1 baseline. Applications deployed as a WAR to an external server need a Servlet 6.1 container; the migration guide advises against anything else. Undertow is not supported in Boot 4.

Step 9. Rehearse and write the rollback

  1. Tag the 4.0.9 build, its image and its dependency lock file so it can be redeployed.
  2. Build the 4.1 target against a copy of production configuration with the same JDK, container and database version.
  3. Run the full test suite and the integration tests against real dependencies, and compare start-up time, memory and error rates with the 4.0 baseline.
  4. Write down the point after which you cannot go back, such as a schema change older code cannot read.

Phase 4: Cut over

Step 10. Release in order and verify

Start with internal applications, then lower-traffic services, then customer-facing ones. Use a canary or blue-green release and watch error rates, latency and the Actuator health endpoint through a full business cycle. Then re-run the step 1 searches, expect no 4.0 results, remove old images, and update the inventory and the end-of-life register.

Phase 5: Plan for what cannot move

Step 11. Choose a cover option and record it

Some applications will not be ready by 31 December: a vendor product certified on 4.0, a change freeze, or a test cycle that needs the first quarter. For each, write down the owner, the target date, the compensating controls and who accepted the risk.

  • Broadcom commercial support: 4.0 is listed to 31 December 2027, per spring.io. Confirm what your own subscription says.
  • Third-party patched builds: OSSeva ships patched, signed Spring Boot 4.0 artifacts, with backported fixes for Spring Boot and the Spring Security 7.0 line it manages, delivered through your own Maven or Gradle repository manager, on the Patch, Assure and Operate tiers. Critical CVEs are patched within 48 hours and High within 7 days (OSSeva's support SLA). See Spring Boot support and Spring continuation.
  • Neither: accept the risk in writing, restrict the application's network exposure, and read which CVEs reach which Spring Boot lines to see what you would be accepting.

Step 12. Put the next date in the calendar

Add 31 July 2027 for Boot 4.1 and Spring Framework 7.0, and 31 December 2027 for Boot 4.2, to whatever register you use. The Spring support calendar lists every Spring Boot, Framework and Security date in one table.

What changes on 31 December 2026

ItemOn the day
Your Spring Boot 4.0 applicationsKeep running. Nothing is switched off.
Open source 4.0 releasesStop. 4.0 fixes after this date ship to commercial customers only.
Open source Spring Security 7.0 releasesStop on the same day. Security 7.1 continues to 31 Jul 2027.
Broadcom commercial support for Boot 4.0Continues to 31 Dec 2027.
Spring Framework 7.0Unaffected: open source support continues to 31 Jul 2027.
Self-managed applications on 4.0 with no other coverNo new public fixes for Boot or Security. Scanners that check lifecycles will flag the version.

One-page printable checklist

DoneStepOwnerEvidence
☐1. Every 4.0 application listedInventory sheet
☐2. Managed and overridden versions recordedDependency tree output
☐3. Every application on 4.0.9Manifest or build output
☐4. Spring Security 7.0 version and features checkedAdvisory notes
☐5. Target chosen per applicationDecision note
☐6. 4.1 removals searched for in code and buildFindings list
☐7. Deprecations cleared on 4.0.9Clean build log
☐8. JDK, build tool and container confirmedBuild matrix
☐9. Rollback tagged and rehearsal runTest log
☐10. Release done, 4.0 removed, register updatedClean inventory
☐11. Cover recorded for every application left on 4.0Signed exception record
☐12. Next dates entered in the calendarRegister entry

Frequently asked questions

When does Spring Boot 4.0 reach end of support?

Open source support ends on 31 December 2026, and spring.io lists commercial support until 31 December 2027.

Will Spring Boot 4.0 applications stop working on 31 December 2026?

No. They keep running. What ends is the open source release stream for 4.0, and for Spring Security 7.0 on the same day.

Which Spring Boot version should I upgrade 4.0 to?

Spring Boot 4.1, supported in open source to 31 July 2027, or 4.2 once it is generally available, supported to 31 December 2027. Both are minor upgrades from 4.0.

Does Spring Boot 4.1 need a new Spring Framework version?

No. Both 4.0.9 and 4.1.2 manage Spring Framework 7.0.10. The move changes Spring Security from 7.0 to 7.1 and several managed libraries, and removes what 4.0 deprecated.

What is the latest Spring Boot 4.0 release?

4.0.9, released on 22 October 2026. It manages Spring Framework 7.0.10 and Spring Security 7.0.8.

Can I get security patches for Spring Boot 4.0 after 2026?

Yes, from Broadcom's commercial releases to 31 December 2027, or from a third-party patched build. OSSeva ships patched, signed Spring Boot 4.0 artifacts on the Patch, Assure and Operate tiers. See Spring Boot 4.0 end of life.

Tags

Spring BootSpring Boot 4.0End of SupportChecklistSpring Security 7.0Spring Framework 7

Get 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.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call