Redis Versions: Release, EOL and Latest Patch for Every Version

Redis 8.10, released on 29 July 2026, is the newest Redis version. The next Redis EOL is 8.0 on 1 December 2026, then 6.2 on 1 April 2027. Redis 7.0 ended on 29 July 2024 at 7.0.15, and 7.2 and 7.4 run to 1 December 2029. Dates checked against redis.io and endoflife.date on 22 October 2026.

Redis Open Source splits each major version into standard and extended releases. Standard releases, the first and intermediate minors such as 8.0, 8.4 and 8.6, get security and critical bug fixes for six months after the next minor ships. Extended releases, the second and final minors of a major such as 8.2, get them for five years from release.

Only your email is required · An engineer replies within 1 business day · No commitment

Latest release
8.10.3
Supported lines
9
End-of-life lines
3
Next end of life
8.0 · 1 Dec 2026

Running Redis 7.0 or older?

Redis 7.0, 6.0 and 5.0 after end of life

Redis 7.0 ended on 29 July 2024, and 6.0 and 5.0 ended in 2022. Nine CVEs in OSSeva's CVE directory were published after 7.0 ended and name a range that covers its last release. The solution page covers patched 6.2 and 7.0 builds, the Amazon ElastiCache costs and the move to Valkey.

Who patches Redis after end of life

OSSeva provides Redis extended support: patched, signed builds for Redis 7.0 after upstream support ends, plus 24/7 operations on the Operate tier.

Redis release timeline

Active SupportSecurity SupportToday

All Redis versions, release dates and end-of-life dates

VersionRelease dateActive SupportEnd of lifeLatest patchCVEs since EOLOSSeva
8.104 months ago(29 Jul 2026)YesYes8.10.3––
8.86 months ago(25 May 2026)Ended 4 months ago(29 Jul 2026)Yes8.8.4––
8.69 months ago(11 Feb 2026)Ended 6 months ago(25 May 2026)Yes8.6.8––
8.41 year ago(18 Nov 2025)Ended 9 months ago(11 Feb 2026)Yes8.4.8––
8.21 year and 3 months ago(4 Aug 2025)Ended 1 year ago(18 Nov 2025)Ends in 3 years and 9 months(1 Sept 2030)8.2.11––
8.0Redis 8.0 end of life1 year and 6 months ago(2 May 2025)Ended 1 year and 3 months ago(4 Aug 2025)Ends in 15 days(1 Dec 2026)8.0.6––
7.4Redis 7.4 end of life2 years and 4 months ago(29 Jul 2024)Ended 1 year and 6 months ago(2 May 2025)Ends in 3 years(1 Dec 2029)7.4.12––
7.2Redis 7.2 end of life3 years and 3 months ago(15 Aug 2023)Ended 2 years and 4 months ago(29 Jul 2024)Ends in 3 years(1 Dec 2029)7.2.17––
7.0Redis 7.0 end of life4 years and 7 months ago(27 Apr 2022)Ended 3 years and 3 months ago(15 Aug 2023)Ended 2 years and 4 months ago(29 Jul 2024)7.0.1599 scored 7.0+ Patched
6.2Redis 6.2 end of life5 years and 9 months ago(22 Feb 2021)Ended 4 years and 7 months ago(27 Apr 2022)Ends in 4 months(1 Apr 2027)6.2.24––
6.06 years and 7 months ago(30 Apr 2020)Ended 5 years and 9 months ago(22 Feb 2021)Ended 4 years and 6 months ago(31 May 2022)6.0.2099 scored 7.0+–
5.08 years and 1 month ago(17 Oct 2018)Ended 6 years and 7 months ago(30 Apr 2020)Ended 4 years and 7 months ago(27 Apr 2022)5.0.1499 scored 7.0+–

Lifecycle data from endoflife.date (MIT licence), refreshed 15 Nov 2026. Upstream policy: redis.io. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for. “CVEs since EOL” counts advisories in OSSeva’s CVE directory that were published after the line ended and whose affected range covers its final release. The directory holds the advisories NVD matches to the product, mostly scored 7.0 or higher, so it is a subset of every advisory.

CVEs published since Redis 7.0 ended

These are the CVEs in OSSeva's CVE directory that name a range covering Redis 7.0.15, the last 7.0 release, and were published after 7.0 ended on 29 July 2024. Redis fixed each in 6.2.x, 7.2.x, 7.4.x or 8.x, so no 7.0 build carries a fix. They are scored from 7.5 up to 9.9. Redis 6.0 and 5.0 ended earlier, so the same nine apply to them.

9 in the directory as of 22 October 2026.

CVECVSSPublishedIssueFixed upstream in
CVE-2024-314498.87 Oct 2024Redis Lua bit library stack buffer overflow may lead to remote code execution6.2.16, 7.2.6, 7.4.1
CVE-2024-469819.86 Jan 2025Redis Lua script can manipulate the garbage collector and lead to remote code execution6.2.17, 7.2.7, 7.4.2
CVE-2025-216057.523 Apr 2025Redis output buffers grow without limit for an unauthenticated client6.2.18, 7.2.8, 7.4.3
CVE-2025-320237.87 Jul 2025Redis HyperLogLog commands allow an out-of-bounds write6.2.19, 7.2.10, 7.4.5, 8.0.3
CVE-2025-468178.83 Oct 2025Redis Lua library commands allow an integer overflow that may lead to remote code execution6.2.20, 7.2.11, 7.4.6, 8.0.4, 8.2.2
CVE-2025-483677.57 Jul 2025Redis unauthenticated connections can starve other clients with repeated protocol errors6.2.19, 7.2.10, 7.4.5, 8.0.3
CVE-2025-498449.93 Oct 2025Redis is an open source, in-memory database that persists on disk.6.2.20, 7.2.11, 7.4.6, 8.0.4, 8.2.2
CVE-2026-236318.15 May 2026Redis is an in-memory data structure store.8.6.3 and later
CVE-2026-252438.85 May 2026Redis is an in-memory data structure store.8.6.3 and later

The directory lists Redis CVEs matched at NVD to the product with a CVSS score of 7.0 or higher, so it is a subset of every Redis advisory. Affected ranges and fixed-in versions are as the MITRE and NVD records publish them. Redis 6.2, 7.2 and 7.4 are still supported and received these fixes.

Running an end-of-life Redis version?

OSSeva keeps end-of-life Redis patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.

Redis extended support

Questions

Redis end of life: common questions

Book a 15-minute call

When does Redis 8.0 reach end of life?

redis.io lists 1 December 2026 as the end-of-life date for Redis 8.0, a standard release. The extended release 8.2 runs to 1 September 2030, and redis.io lists no end date yet for 8.4 to 8.10. Dates checked 22 October 2026.

Is Redis 6.2 end of life?

Redis 6.2 is an extended release, and redis.io lists 1 April 2027 as its end-of-life date. Until then it receives security updates and critical bug fixes only. Teams on 6.2 need to move to another extended line, 7.2, 7.4 or 8.2, or arrange other support, when that date arrives.

Is Redis 7.0 end of life?

Yes. Redis 7.0 is not on the list of supported versions at redis.io, and endoflife.date records its support ending on 29 July 2024, when Redis 7.4 shipped. Its last release was 7.0.15 in January 2024. Users on 7.0 can move to 7.2 or 7.4, both extended releases with fixes until 1 December 2029.

When does Redis 7.2 reach end of life?

redis.io lists 1 December 2029 as the end-of-life date for both Redis 7.2 and 7.4, which are extended releases. Until then they receive security updates and critical bug fixes. Redis 8.2, also extended, runs to 1 September 2030, while the standard release 8.0 has a much shorter window, with an end-of-life date of 1 December 2026.

What is the latest Redis version?

8.10.3, released 26 Oct 2026, on the 8.10 line. Other supported lines: 8.8, 8.6, 8.4, 8.2, 8.0, 7.4, 7.2 and 6.2.

When is the next Redis end of life?

Redis 8.0 reaches the end of security support on 1 Dec 2026. After that date the project stops shipping security fixes for 8.0, and CVEs disclosed later stay unpatched upstream.

Which Redis versions are still supported?

8.10, 8.8, 8.6, 8.4, 8.2 (until 1 Sept 2030), 8.0 (until 1 Dec 2026), 7.4 (until 1 Dec 2029), 7.2 (until 1 Dec 2029) and 6.2 (until 1 Apr 2027). Every other line has reached end of life, per the dates in the table above.

Can I get security patches for an end-of-life Redis version?

Yes. OSSeva ships signed builds with backported CVE fixes for Redis 7.0 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.

Who provides Redis support after end of life?

OSSeva provides Redis extended support: patched, signed builds for Redis 7.0 after upstream support ends, plus 24/7 operations on the Operate tier.

Get a quote

Still running an end-of-life Redis?

Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call