OSSEVA FOR REDIS
Redis — patched, protected, operated.
Drop-in CVE patches for Redis 6.2.x and 7.0.x, including the community-EOL versions Redis Ltd. and Broadcom no longer support. OSSeva keeps your Redis stack patched, compliant, and under a clear operational SLA.
Why now
Redis license changed to BSL in 2024 — community forked to Valkey
Redis Ltd. changed Redis 7.4+ from BSD to the Business Source License (BSL) in March 2024. The open-source community forked Redis as Valkey. Enterprise teams on Redis 6.x–7.0.x are stuck between the old BSD license and no upstream patches.
CVE-2026-32901 — heap overflow in XAUTOCLAIM
A critical heap overflow in Redis 6.2.x–7.0.x XAUTOCLAIM command processing was disclosed in May 2026. Redis Ltd. patched only 7.2.x+. OSSeva shipped a backport for 6.2.x and 7.0.x within 48 hours.
Redis Enterprise pricing at $X per 25GB RAM
Redis Enterprise pricing scales with memory — directly mirroring your cache footprint. For large-footprint Redis deployments in financial services or media, the delta between Redis Enterprise and OSSeva-supported community Redis is material.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 6.2.x(Full CVE coverage) | Extended | Clean |
| 7.0.x(1 patch in test) | Extended | 1 open |
| 7.2.x | Current | Clean |
| Valkey 7.2.x(BSD fork) | Current | Clean |
| Valkey 8.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 Redis 6.2.x–7.0.x under the original BSD license.
- Quarterly CVE patches for Redis 6.2.x and 7.0.x
- Heap overflow and memory corruption priority coverage
- Docker / apt / yum delivery
- Signed artifacts (GPG)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus Redis security hardening and compliance documentation.
- Everything in Patch
- Redis ACL and authentication configuration audit
- Persistence (RDB/AOF) security configuration review
- SOC 2 / PCI DSS attestation package
- Redis Cluster topology security review
- TLS/SSL configuration hardening guide
- 24/7 managed operations
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min SLA, named Redis engineers.
- Everything in Assure
- 24/7 instance and cluster health monitoring
- 15-minute P1 incident response SLA
- Named senior Redis engineer on your account
- Memory usage and eviction policy alerting
- Replication lag monitoring
- Quarterly performance reviews
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.
docker pull artifacts.osseva.io/redis:7.0.15-osseva-1
docker run -d \
--name redis \
-p 6379:6379 \
-v redis-data:/data \
artifacts.osseva.io/redis:7.0.15-osseva-1 \
redis-server --requirepass yourpassword --appendonly yes# Add OSSeva apt repository
curl -fsSL https://packages.osseva.io/gpg | sudo gpg --dearmor -o /usr/share/keyrings/osseva.gpg
echo "deb [signed-by=/usr/share/keyrings/osseva.gpg] https://packages.osseva.io/apt stable main" \
| sudo tee /etc/apt/sources.list.d/osseva.list
sudo apt-get update
sudo apt-get install -y osseva-redis=7.0.15-osseva-1Migrate from Redis Enterprise
Redis Enterprise charges per 25GB RAM across your deployment. For large-footprint caching and session store deployments, OSSeva-supported community Redis provides the same CVE coverage and operational SLAs at a fraction of the cost.
Pricing model
OSSeva for Redis is priced per instance cluster — not per GB of memory, not per operation. 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 Redis 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.