Redis End of Life Dates
database
Developers rely on Redis, a popular in-memory database, to power their applications with high performance and low latency. Created to solve the problem of slow disk-based databases, Redis has been a go-to solution since its inception. The Redis project is actively maintained by Redis Labs, ensuring that the database stays up-to-date with the latest security patches and features. With its ability to handle large amounts of data and provide sub-millisecond response times, it's no wonder that developers flock to Redis for their database needs.
The end-of-life landscape for Redis is complex, with a total of 11 versions, 5 of which have already reached their end-of-life. Currently, 6 versions are still actively supported, giving developers a range of options to choose from. The latest stable version, 6.2.22, is the recommended version for new deployments. Although there is no next scheduled end-of-life date, the last version to reach end-of-life was version 8.2, which occurred on 2026-05-25. This highlights the importance of staying on top of version updates to ensure continuity and security.
When it comes to security, Redis has a total of 26 tracked CVEs, with none being critical. The most affected version is 7.2, with 3 reported CVEs. Despite the lack of critical vulnerabilities, it's still essential for developers to keep their Redis instances up-to-date with the latest security patches to prevent potential issues. By tracking the end-of-life dates and security timelines, developers can plan their upgrades and ensure the continuity and security of their applications. With no known exceptions or KEV status applicable, developers should focus on regularly reviewing and updating their Redis versions to maintain the highest level of security and performance.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 8.8 | May 25, 2026 | — | No | — | 8.8.1 | — | Active | |
| 8.6 | Feb 11, 2026 | May 25, 2026 | No | — | 8.6.5 | Active | ||
| 8.4 | Nov 18, 2025 | Feb 11, 2026 | No | — | 8.4.5 | Active | ||
| 8.2 | Aug 4, 2025 | Nov 18, 2025 | May 25, 2026 | 60d ago | 8.2.8 | EOL | ||
| 8.0 | May 2, 2025 | Aug 4, 2025 | Feb 11, 2026 | 163d ago | 8.0.6 | EOL | ||
| 7.4 | Jul 29, 2024 | May 2, 2025 | No | — | 7.4.9 | Active | ||
| 7.2 | Aug 15, 2023 | Jul 29, 2024 | No | — | 7.2.14 | Active | ||
| 7.0 | Apr 27, 2022 | Aug 15, 2023 | Jul 29, 2024 | 725d ago | 7.0.15 | EOL | ||
| 6.2 | Feb 22, 2021 | Apr 27, 2022 | No | — | 6.2.22 | Active | ||
| 6.0 | Apr 30, 2020 | Feb 22, 2021 | May 31, 2022 | 1515d ago | 6.0.20 | EOL | ||
| 5.0 | Oct 17, 2018 | Apr 30, 2020 | Apr 27, 2022 | 1549d ago | 5.0.14 | EOL |
Data sourced from endoflife.date · CVE data from NVD
