OSSEVA FOR SPRING FRAMEWORK
Spring Framework 5.x is EOL. Your applications are not.
OSSeva ships CVE patches for Spring Framework 5.3.x and earlier past the community EOL date — with migration design to 6.x and compliance documentation for your auditors.
Why now
Spring Framework 5.3.x: EOL December 2024
Broadcom/VMware set Spring Framework 5.3.x EOL for December 31, 2024. Critical CVEs discovered after that date have no official patch from the upstream project. OSSeva fills that gap.
Migration to Spring 6 requires Java 17+
Spring Framework 6.x requires Java 17 as the baseline. Many enterprise applications are still on Java 11 or 8. The migration is real work — OSSeva gives your team time to do it safely.
Spring Commercial is a commercial product now
Spring Commercial (from Broadcom/VMware) requires a commercial subscription for extended Spring support. OSSeva provides the same CVE-patched continuity under an OSS-compatible contract.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 5.2.x | Extended | Clean |
| 5.3.x | Extended | Clean |
| 6.0.x | Current | Clean |
| 6.1.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 remediation for Spring 5.x past community EOL.
- Quarterly CVE patches for covered versions
- Maven Central compatible artifacts
- Vulnerability disclosure notifications
- Migration planning
- Architecture review
OSSeva Assure
Patches plus 5.x → 6.x migration design and compliance docs.
- Everything in Patch
- Spring 5→6 migration roadmap
- Dependency compatibility audit
- Compliance attestation package
- Spring Security coverage included
- 24/7 managed operations
OSSeva Operate
Application-tier managed operations for your Spring fleet.
- Everything in Assure
- JVM performance monitoring
- 15-minute P1 incident response SLA
- Named engineer on your account
- 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.
<dependency>
<groupId>io.osseva.springframework</groupId>
<artifactId>spring-core</artifactId>
<version>5.3.39-osseva-1</version>
</dependency>implementation("io.osseva.springframework:spring-core:5.3.39-osseva-1")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 Framework 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.