OSSEVA FOR SPRING BOOT
Spring Boot 2.x reached EOL. Your workloads didn't.
OSSeva ships CVE patches for Spring Boot 2.6.x and 2.7.x — the versions running in production at most Fortune 500 enterprises. No forced Spring Boot 3 migration. No Java 17 requirement. Your timeline.
Why now
Spring Boot 2.x community EOL: November 2023
Broadcom ended community support for all Spring Boot 2.x versions in November 2023. Critical CVEs discovered after that date have no upstream patch path — but your auditor's checklist hasn't changed.
Spring Boot 3 requires Java 17 minimum
Upgrading from Spring Boot 2.x to 3.x requires Java 17 as the minimum JDK, plus Spring Security reconfiguration, Jakarta namespace migrations, and dependency compatibility validation. For most enterprises, that's a 6–18 month project.
CVE-2026-38912 — SpEL injection in Spring Framework 5.3.x
A critical SpEL injection vulnerability in Spring Framework 5.3.x (the foundation of Spring Boot 2.x) was disclosed in May 2026. OSSeva shipped a patched build within 48 hours. The upstream project will not backport this fix.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 2.6.x(Full CVE coverage) | Extended | Clean |
| 2.7.x(Full CVE coverage) | Extended | Clean |
| 3.0.x(STS — community EOL) | EOL | 2 open |
| 3.1.x(STS — community EOL) | EOL | 1 open |
| 3.2.x | Current | Clean |
| 3.3.x | Current | Clean |
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
CVE patches for Spring Boot 2.x. Signed artifacts, repo manager delivery.
- Quarterly CVE patches for Spring Boot 2.6.x and 2.7.x
- Spring Framework 5.3.x patches included
- Maven Central / private repo delivery
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications within 24 hours
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus audit documentation and Spring 3 migration planning.
- Everything in Patch
- SOC 2 / HIPAA / PCI attestation package
- Spring Boot 3 migration readiness assessment
- Java version upgrade sequencing plan
- Spring Security reconfiguration guidance
- Annual architecture review
- 24/7 managed operations
OSSeva Operate
Full MSP: monitoring, 15-min SLA, named Spring engineers.
- Everything in Assure
- 24/7 application performance monitoring
- 15-minute P1 incident response SLA
- Named senior Spring engineer on your account
- Dependency vulnerability scanning (transitive)
- Quarterly business reviews
- Spring Boot 3 migration execution support
All tiers priced per cluster/application — not per core. Contact for pricing →
How it installs
OSSeva artifacts arrive via your existing package infrastructure. Pull the patched version the same way you pull upstream today — just from the OSSeva registry.
<dependencyManagement>
<dependencies>
<dependency>
<groupId>io.osseva.spring</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>2.7.18-osseva-2</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>repositories {
maven {
url "https://artifacts.osseva.io/maven"
credentials {
username System.getenv("OSSEVA_USER")
password System.getenv("OSSEVA_TOKEN")
}
}
}
dependencies {
implementation platform("io.osseva.spring:spring-boot-dependencies:2.7.18-osseva-2")
implementation "org.springframework.boot:spring-boot-starter-web"
}Migrate from Broadcom Spring Commercial
Broadcom commercialized the Spring ecosystem in 2023. OSSeva provides continuation coverage for the community versions your applications run today — with a clear migration path to Spring Boot 3 when your team is ready.
Pricing model
OSSeva for Spring Boot is priced per application — not per developer seat or per deployment unit. Contact for scoping.
Compliance library
Frequently asked questions
Which versions of RabbitMQ are past community end-of-life?
RabbitMQ 3.8.x, 3.9.x, 3.10.x, 3.11.x, and 3.12.x have all reached community EOL — meaning no further security patches or CVE fixes are released by the RabbitMQ maintainers for those versions. RabbitMQ 3.13.x reached EOL in late 2024. OSSeva delivers backported CVE patches for 3.11 through 3.13.
Which PostgreSQL versions are no longer receiving community security patches?
PostgreSQL 9.6 through 13 have all reached community EOL. PostgreSQL 11 reached EOL November 2023, PostgreSQL 12 reached EOL November 2024, and PostgreSQL 13 reaches EOL November 2025. OSSeva provides extended security patching for PostgreSQL 11, 12, and 13 for teams that cannot immediately migrate to PG 14 or later.
Is Spring Framework 5.3.x still supported?
Spring Framework 5.3.x reached its community OSS EOL on December 31, 2024. Broadcom's commercial support for Spring 5.3.x is also no longer available under standard terms. OSSeva delivers backported CVE patches for Spring Framework 5.3.x and Spring Boot 2.7.x under our extended lifecycle support program.
Which versions of Apache Kafka are EOL?
Apache Kafka versions 2.x and 3.0 through 3.4 are past their community supported window, meaning no further patch releases. Kafka 3.5 and 3.6 have reached or are approaching EOL. OSSeva supports Kafka 2.8 through 3.5 with backported security patches and compliance documentation.
What happened to Redis licensing? Can I still use Redis for free?
In March 2024, Redis Ltd. changed the Redis license from BSD-3-Clause to the Business Source License (BSL 1.1), which restricts use in competing database products. The Valkey project (a Linux Foundation fork) continues under BSD-3-Clause. OSSeva maintains BSD-licensed, CVE-patched builds of Redis 6.2 and 7.0 for enterprises that need verifiable open-source licensing alongside security coverage.
Is Node.js 18 still receiving security patches?
Node.js 18 (LTS 'Hydrogen') reached its end-of-life date in April 2025 and no longer receives security releases from the Node.js project. OSSeva delivers CVE patches for Node.js 18 for enterprise teams that have not yet migrated to Node.js 20 or 22.
Is Apache Tomcat 8.5 still supported?
Apache Tomcat 8.5 reached its community EOL in March 2024. OSSeva provides extended security patching for Tomcat 8.5.x for teams running Java EE 7 workloads that cannot immediately migrate to Tomcat 9.0 or 10.1.
What .NET versions does OSSeva support?
.NET 6 reached Microsoft end-of-support in November 2024. .NET 7 reached EOL in May 2024. OSSeva delivers CVE patches for .NET 6 and .NET 7 for teams that have not yet migrated to .NET 8 (LTS, supported through November 2026).
Ready to get Spring Boot patched and supported?
Start with a 45-minute discovery call. We confirm your version coverage, scope the engagement, and have you onboarded within your first quarter.