OSSEVA FOR SPRING SECURITY
Spring Security 5.x reached EOL. Your auth layer didn't get safer.
Authentication and authorization vulnerabilities are the most severe class of application CVEs. OSSeva maintains CVE coverage for Spring Security 5.7.x and 5.8.x — the versions protecting most enterprise Spring applications today.
Why now
Spring Security 5.x community EOL: December 2023
All Spring Security 5.x versions reached community end-of-life in December 2023. Any new authentication bypass, CSRF, or authorization vulnerability discovered after that date has no upstream patch path.
Auth/authz CVEs carry the highest compliance risk
Authentication and authorization vulnerabilities in Spring Security map directly to PCI DSS Requirement 6, HIPAA §164.312, and SOC 2 CC6. An unpatched auth layer is an automatic finding in most compliance audits.
Spring Security 6.x requires Jakarta namespace migration
Upgrading to Spring Security 6.x requires migrating from javax.* to jakarta.* namespaces — a non-trivial change that touches every layer of a Spring application. OSSeva covers 5.x while your team executes that migration.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 5.6.x(Full CVE coverage) | Extended | Clean |
| 5.7.x(Full CVE coverage) | Extended | Clean |
| 5.8.x(Full CVE coverage) | Extended | Clean |
| 6.0.x(STS — community EOL) | EOL | 1 open |
| 6.1.x(STS — community EOL) | EOL | Clean |
| 6.2.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 Security 5.x. Authentication layer protection.
- Quarterly CVE patches for Spring Security 5.6.x–5.8.x
- Emergency patches for authentication bypass CVEs
- Maven Central / private repo delivery
- Signed artifacts (GPG)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus security configuration audit and compliance documentation.
- Everything in Patch
- Spring Security configuration audit
- OAuth 2.0 / OIDC configuration review
- SOC 2 / PCI DSS attestation package
- Spring Security 6 migration assessment
- Pen-test validation summary
- 24/7 managed operations
OSSeva Operate
Full MSP with security event monitoring and named engineers.
- Everything in Assure
- 24/7 auth event monitoring and alerting
- 15-minute P1 response for auth bypass incidents
- Named senior Spring Security engineer
- Session management and token security reviews
- Quarterly security posture reviews
- Spring Security 6 migration execution
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.spring</groupId>
<artifactId>spring-security-core</artifactId>
<version>5.8.12-osseva-1</version>
</dependency>
<dependency>
<groupId>io.osseva.spring</groupId>
<artifactId>spring-security-web</artifactId>
<version>5.8.12-osseva-1</version>
</dependency>dependencies {
implementation "io.osseva.spring:spring-security-core:5.8.12-osseva-1"
implementation "io.osseva.spring:spring-security-web:5.8.12-osseva-1"
implementation "io.osseva.spring:spring-security-config:5.8.12-osseva-1"
}Migrate from Broadcom Spring Commercial
Broadcom commercialized Spring Security alongside the broader Spring ecosystem. OSSeva provides continuation coverage for 5.x with a structured path to Spring Security 6 when your Jakarta namespace migration is complete.
Pricing model
OSSeva for Spring Security is typically bundled with Spring Boot and Spring Framework coverage. Contact for combined pricing.
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 Security 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.