Back to blog

OSSeva Blog

Operations

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

9 min read

The short answer

Spring Boot 3.4 reaches the end of commercial support on 31 December 2026. Its open source support already ended on 31 December 2025, and the last open source release, 3.4.13, came out on 18 December 2025. To prepare: find every 3.4 application, work out which of the two dates applies to you, choose a target, rehearse the upgrade and decide cover for anything that cannot move.

The two dates matter because they describe different things. If you have no Spring Enterprise subscription, 3.4 has had no public fixes for almost a year, and 31 December 2026 changes nothing for you. If you do have one, that date is the day your vendor fixes stop. The steps are the same either way. This checklist covers the Boot line; Spring Boot 3.4 end of life carries the CVEs published since open source support ended.

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 3.4?

LineOpen source support endedCommercial support endsWhat it means
Spring Boot 3.4.x31 Dec 202531 Dec 2026Last open source release 3.4.13 (18 Dec 2025). Later 3.4 releases are commercial only.
Spring Framework 6.2.x (managed by 3.4)30 Jun 202630 Jun 2032Framework 6.2 is the longest-lived layer under 3.4.
Spring Security 6.4.x (managed by 3.4)31 Dec 202531 Dec 2026Last open source release 6.4.13. Ends on the same day as Boot 3.4.
Spring Boot 3.5.x (the next line)30 Jun 202630 Jun 2032The last 3.x line. Moving to it keeps vendor support to 2032 but restores no open source fixes.

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 support tab shows months; the generations data gives the day. Broadcom's support policy says the last minor version of a major line gets five more years of enterprise support, which is why 3.5 runs to 2032 and 3.4 does not. Check the dates in your own contract: the policy page says the support tab "does not define the enterprise support policy".

Phase 1: Find and inspect

Step 1. List every Spring Boot 3.4 application

Search source, builds and running systems. A Boot jar records its version in the manifest, which is the fastest check on a deployed artifact.

grep -rn --include=pom.xml -A2 "spring-boot-starter-parent" . | grep -E "<version>3\.4\."
grep -rnE --include="build.gradle*" --include="settings.gradle*" --include="*.toml" "org.springframework.boot.*3\.4\." .
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}'

Then look for the applications nobody lists: batch jobs, internal tools, vendor products that embed Spring Boot, and services whose parent POM is a company-wide BOM that pins 3.4 for everyone. For each one, record the owner, the environment and whether it faces the internet.

Step 2. Decide which date applies to each application

Use the table above. An application with no Spring Enterprise subscription is already past all support for 3.4. An application with one has until 31 December 2026. An application a supplier ships to you has the supplier's date, so ask for it in writing.

Step 3. Record what Boot 3.4 manages in each one

Boot's value is the curated dependency set, so the end date reaches every library it manages. Print the resolved versions.

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

Spring Boot 3.4.13 manages Spring Framework 6.2.15, Spring Security 6.4.13, Tomcat 10.1.50, Jackson 2.18.5 and Hibernate 6.6.39.Final, from its published dependency versions. Anything you override sits outside that set, so list the overrides too. Spring Cloud and other projects Boot does not manage need a release train that matches the Boot line; check each against its own compatibility table before choosing a target.

Step 4. Record the Java version, build tool and container

Spring Boot 3.x needs Java 17 or later, and so does 4.x. Boot 4.0 and later also expect Gradle 8.14 or later (or Gradle 9) and Maven 3.6.3 or later, and embed Tomcat 11 or Jetty 12.1 on a Servlet 6.1 baseline, according to Boot's system requirements for 4.0.9. Record the JDK and the build tool for every application now, because they set how far you can move in one step.

Step 5. Pull the current advisories for each line under 3.4

Spring Framework 6.2 left open source support on 30 June 2026. CVE-2026-59313 affects Spring Framework 6.2.0 to 6.2.19, and spring.io lists the 6.2 fix, 6.2.20, as Enterprise Support Only. Spring Security 6.4 has the same pattern: CVE-2026-22732, where Spring Security's HTTP headers may not be written, lists 6.4.15 as Enterprise Support Only. Check the CVE directory and spring.io's advisory list for the ones that reach your lines, and note which fixes you can get without a subscription.

Phase 2: Choose the path

Step 6. Pick the target for each application

TargetOpen source support endsCommercial support endsLatest release (13 Nov 2026)Use it when
Spring Boot 3.530 Jun 2026 (ended)30 Jun 20323.5.16You need the smallest change and have a Spring Enterprise subscription. It is also the step Boot 4's migration guide asks for first.
Spring Boot 4.031 Dec 202631 Dec 20274.0.9Rarely. Its open source support ends on the same day 3.4's commercial support does.
Spring Boot 4.131 Jul 202731 Jul 20284.1.2You want open source fixes and can take the Boot 4 changes.
Spring Boot 4.231 Dec 202731 Dec 20284.2.0-RC2 on Maven Central; spring.io lists a November 2026 releaseYou can wait for general availability.

The Boot 4 migration guide says to upgrade to the latest 3.5.x first, so any route to 4.x goes through 3.5. If the application has to leave 3.4 by 31 December, 3.5 is a quick first move and 4.1 is the target that restores open source support.

Step 7. Read what Boot 4 removes before you commit

The 4.0 migration guide lists the points that stop most upgrades: Java 17 or later, Kotlin 2.2 or later and GraalVM 25 or later for native images; a Jakarta EE 11 and Servlet 6.1 baseline with Spring Framework 7; every class, method and property deprecated in 3.x removed; Undertow dropped, including its starter; and the embedded launch scripts for fully executable jars removed. Boot 4.0.9 manages Jackson 3 alongside Jackson 2. The guide's property helper prints diagnostics at startup and migrates renamed properties at runtime while you work:

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-properties-migrator</artifactId>
  <scope>runtime</scope>
</dependency>

Remove it when the migration is done, as the guide says. The code-level changes, with a search for each, are in the Spring Boot 3.5 to 4 upgrade guide.

Phase 3: Rehearse and protect

Step 8. Clear deprecations on 3.5 first

Move the application to the latest 3.5.x, build with deprecation warnings on, and clear them. Everything deprecated in 3.x is removed in 4.0, so each warning you clear now is a compile error you do not meet later.

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

Step 9. Capture the rollback and rehearse on a production-shaped copy

  1. Keep the 3.4 build, its container image and its dependency lock file under a tag you can redeploy.
  2. Build the target against a copy of production configuration, with the same JDK, container and database version.
  3. Run the full test suite, then the integration tests against real dependencies. Compare start-up time, memory and error rates with the 3.4 baseline.
  4. Write down the point after which you cannot go back, such as a database migration that older code cannot read.

Phase 4: Cut over

Step 10. Release in order, smallest blast radius first

Start with internal applications, then lower-traffic services, then the ones that face customers. Use a canary or a blue-green release, watch error rates, latency and the Actuator health endpoint through a full business cycle, and keep the 3.4 release ready until the window you set in step 9 closes.

Step 11. Verify and clean up

Re-run the step 1 searches and expect no 3.4 results. Remove old images from registries, update the inventory and the end-of-life register, and confirm that scanners no longer report 3.4, Framework 6.2 or Security 6.4 against the application.

Phase 5: Plan for what cannot move

Step 12. Choose a cover option and record it

Some applications will not move by 31 December: a vendor product certified on 3.4, a framework migration that needs a longer test cycle, or a change freeze. For each, write down the owner, the target date, the compensating controls and who accepted the risk.

  • Broadcom commercial support: 3.4 is listed to 31 December 2026 and 3.5 to 30 June 2032, per spring.io. Confirm what your own subscription says.
  • Third-party patched builds: OSSeva ships patched, signed Spring Boot 3.4 artifacts with backported fixes for Boot and for the Spring Framework 6.2 and Spring Security 6.4 lines 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.

What changes on 31 December 2026

ItemOn the day
Your Spring Boot 3.4 applicationsKeep running. Nothing is switched off.
Open source 3.4 releasesNo change. The last was 3.4.13, in December 2025.
Broadcom commercial support for Boot 3.4 and Spring Security 6.4Ends. No vendor releases for either line after this date.
Spring Framework 6.2Unaffected: commercial support continues to 30 Jun 2032.
Self-managed applications with no other coverNo supplier fixes for Boot or Security. Scanners that check lifecycles will flag the version.

One-page printable checklist

DoneStepOwnerEvidence
☐1. Every 3.4 application listedInventory sheet
☐2. End date decided per applicationDate and source per application
☐3. Managed and overridden versions recordedDependency tree output
☐4. JDK, build tool and container recordedBuild matrix
☐5. Advisories for Boot, Framework 6.2 and Security 6.4 reviewedAdvisory list
☐6. Target chosen per applicationDecision note
☐7. Boot 4 removals read against the codebaseFindings list
☐8. Deprecations cleared on the latest 3.5.xClean build log
☐9. Rollback tagged and rehearsal runTest log
☐10. Release done in orderChange ticket
☐11. Verification done and 3.4 removedClean inventory
☐12. Cover recorded for every application left on 3.4Signed exception record

Frequently asked questions

When does Spring Boot 3.4 reach end of support?

Commercial support ends on 31 December 2026, per spring.io. Open source support ended on 31 December 2025, and the last open source release was 3.4.13.

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

No. They keep running. What ends is Broadcom's commercial support for the 3.4 line, and it ends for Spring Security 6.4 on the same day.

Is Spring Boot 3.5 supported?

Not in open source: that ended on 30 June 2026. Broadcom's commercial support for 3.5 runs to 30 June 2032, because it is the last minor of the 3.x line.

Which Spring Boot version should I upgrade 3.4 to?

Spring Boot 4.1, by way of the latest 3.5.x, if you want open source fixes: 4.1 is supported to 31 July 2027. Boot 4.0 ends on 31 December 2026, so it is a poor target.

What Java version does Spring Boot 4 need?

Java 17 or later, the same minimum as Boot 3. Kotlin projects need 2.2 or later, and native images need GraalVM 25 or later, per the Boot 4.0 migration guide.

Can I get security patches for Spring Boot 3.4 after the date?

Yes, from a third-party patched build. OSSeva ships patched, signed Spring Boot 3.4 artifacts on the Patch, Assure and Operate tiers. See Spring Boot 3.4 end of life.

Tags

Spring BootSpring Boot 3.4End of SupportChecklistSpring Framework 6.2Spring Security 6.4

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