Redis 8.0 end of life
Redis 8.0 reaches end of life on 1 December 2026, according to redis.io's version management page. The last 8.0 release, 8.0.6, shipped on 23 February 2026, so the security fixes released on 5 May 2026 reached 8.2, 8.4 and 8.6 but not 8.0. Upgrade to 8.2, an extended release supported until 1 September 2030.
What now
Which vendors provide Redis 8.0 security patches after 1 December 2026?
Redis EOL: Extended Support for Redis 6 and 7- End of life
- 1 December 2026
- Released
- May 2025
- Final release
- 8.0.6 (23 February 2026)
- Successor
- Redis 8.2 (extended release, supported to 1 September 2030)
Date published by redis.io Redis Open Source version management. We do not publish a lifecycle date we cannot source. Dates checked against redis.io's version management page, the Redis GitHub releases and endoflife.date on 11 November 2026.
Last reviewed
Redis versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Redis 8.0 (this page) | 2 May 2025 | 1 December 2026 | Approaching |
| Redis 7.4 | 29 Jul 2024 | 1 December 2029 | Supported |
| Redis 7.2 | 15 Aug 2023 | 1 December 2029 | Supported |
| Redis 7.0 | 27 Apr 2022 | 29 July 2024 | End of life |
| Redis 6.2 | 22 Feb 2021 | 1 April 2027 | Approaching |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 1 December 2026
- On 1 December 2026 redis.io's list gives 8.0 no further security updates or critical bug fixes. 8.0 is a standard release, the first release in the 8 series, and standard releases are the short-lived kind.
- Most of that has already happened. The last 8.0 release is 8.0.6, from 23 February 2026. The 8.2, 8.4 and 8.6 lines each took a security release on 5 May 2026 and another on 26 October 2026, and 8.0 took neither.
- Fixes for new advisories will not come to 8.0. Three advisories published on 5 May 2026 cover a range that includes 8.0, and their fixes exist only in later lines.
What actually breaks in the upgrade
8.2 is the target if you want a date; 8.4 and later are a treadmill
8.2 is the second minor release of the 8 series, an extended release, supported until 1 September 2030. 8.4, 8.6, 8.8 and 8.10 are standard releases with no end date yet, and each stops getting fixes six months after its successor ships. A cluster on a standard line has to move again within months. A cluster on 8.2 does not, though it gives up the features that came after 8.2.
Data files: 8.0, 8.2 and 8.4 write the same format, 8.6 does not
Redis's source has RDB version 12 on the 8.0, 8.2 and 8.4 branches and version 13 on 8.6. A server refuses an RDB file written by a newer format than it knows, so an 8.0 to 8.2 or 8.4 move keeps a way back by file, and a move to 8.6 or later does not. Test a restore on 8.0 before you rely on it either way, and keep the 8.0 primary until the rollback window has closed.
Redis publishes no 8.0 to 8.x upgrade page
The upgrade pages on redis.io cover Redis 8 from 7.x and from Redis Stack 7.2 and 7.4. There is no page for moving within the 8 series, so treat it as a minor-version upgrade you rehearse. Build the new version as a replica of the 8.0 primary on production-sized data with real clients, check replication, then fail over. Cluster mode needs the same rehearsal on a cluster.
The licence does not change inside 8
Redis 8.0.0 and later are available under RSALv2, SSPLv1 or AGPLv3, so moving from 8.0 to 8.2 keeps the same three options. The modules for search, JSON, time series and probabilistic types ship inside Redis from 8 with the same version number as the server, so one upgrade moves them together. If you want a BSD licence, that is a separate decision: Valkey documents compatibility with Redis OSS 7.2 and earlier, not with 8.0, so leaving from 8.0 is a migration to design and test, not an upgrade.
When does each Redis 8 release line end?
Redis publishes two release types. A standard release gets security updates and critical bug fixes for six months after the following minor version ships. An extended release, the second minor of a series or the final one, gets them for five years from its release date. redis.io's table shows an end-of-life date only for 8.0 and 8.2. The newer standard lines show TBD, because each one's window is set by when its successor ships.
For 8.0 the release history is the better guide than the table. 8.2 shipped on 4 August 2025 and the last 8.0 release came on 23 February 2026, about six months later, which is what the six-month rule predicts. The table's 1 December 2026 is the formal date. Nothing has come for 8.0 in the eight months since February, while 8.2, 8.4 and 8.6 all took another security release on 26 October 2026. Its 8.2.11 notes list a heap buffer overflow over the cluster bus in cluster mode, which we have not checked against 8.0.
Redis Open Source 8.x lines on redis.io's version management page
| Version | Release type | End of life (redis.io) | Latest release checked |
|---|---|---|---|
| 8.10 | Standard | TBD | 8.10.3 (26 Oct 2026) |
| 8.8 | Standard | TBD | 8.8.4 (26 Oct 2026) |
| 8.6 | Standard | TBD | 8.6.8 (26 Oct 2026) |
| 8.4 | Standard | TBD | 8.4.8 (26 Oct 2026) |
| 8.2 | Extended | 1 Sep 2030 | 8.2.11 (26 Oct 2026) |
| 8.0 | Standard | 1 Dec 2026 | 8.0.6 (23 Feb 2026) |
Source: redis.io Redis Open Source version management and the redis/redis GitHub releases, checked 11 November 2026. endoflife.date agrees on the 8.0 and 8.2 dates.
Which security fixes did Redis 8.0 miss?
The last Redis 8.0 release is 8.0.6, from 23 February 2026. On 5 May 2026 Redis shipped 8.2.6, 8.4.3 and 8.6.3, and 7.2.14 and 7.4.9 for the older lines, with fixes for five security issues. No 8.0 release followed. Three of the five have GitHub advisories whose affected ranges include 8.0, and they are listed here.
The other two, CVE-2026-25588 and CVE-2026-25589, fix RESTORE problems in the Time Series and Probabilistic modules. We have not checked whether 8.0 is affected, so they are not in the table.
Redis security fixes of 5 May 2026 whose advisories cover Redis 8.0
| CVE | CVSS | Published | Issue | Affected, per Redis advisory | Fixed in |
|---|---|---|---|---|---|
| CVE-2026-25243 | 8.8 | 5 May 2026 | RESTORE command: invalid memory access, possible remote code execution | All Redis versions | 8.2.6, 8.4.3, 8.6.3 (and 7.2.14, 7.4.9). No 8.0 release. |
| CVE-2026-23631 | 8.1 | 5 May 2026 | Lua use-after-free on a replica with replica-read-only disabled | All versions with Lua scripting | 8.2.6, 8.4.3, 8.6.3 (and 7.2.14, 7.4.9). No 8.0 release. |
| CVE-2026-23479 | 8.8 | 5 May 2026 | Use-after-free when a blocked client is evicted | Redis 7.2 or newer | 8.2.6, 8.4.3, 8.6.3 (and 7.2.14, 7.4.9). No 8.0 release. |
Sources: Redis GitHub security advisories GHSA-c8h9-259x-jff4, GHSA-8ghh-qpmp-7826 and GHSA-93m2-935m-8rj3, and the release notes of 8.2.6, 8.4.3, 8.6.3, 7.2.14 and 7.4.9, checked 11 November 2026. The advisories list patched versions as TBD, so the fixed-in column comes from the release notes. CVSS is the score in OSSeva's CVE directory. All three need an authenticated client.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to Redis 8.2 | A move within the 8 series to the extended release, supported to 1 September 2030. | A rehearsal on a replica, then a failover; clients and modules are already on the 8 series | Engineering time | The right destination for most 8.0 estates: one move, and the date runs for four more years. |
| Upgrade to 8.4 or newer | The newest features, on standard releases with no end date set. | As for 8.2, plus a decision about the RDB format change at 8.6 | Engineering time, then a move every few months | Worth it when you need a feature that is not in 8.2. Plan to keep moving. |
| Move to Valkey | A BSD-licensed fork. Its documentation promises compatibility with Redis OSS 7.2 and earlier. | A migration to design and test; compatibility with 8.0 data and features is not documented | Engineering time | A licence decision, not a way to avoid an upgrade. See the Valkey comparison. |
| Stay on 8.0 | No release since 23 February 2026 and none coming after 1 December 2026. | None | Zero now | Hard to defend. Three advisories published on 5 May 2026 reach 8.0 and have no 8.0 fix. |
What OSSeva does for Redis 8.0
OSSeva supports this line
OSSeva lists Redis 8.x as a current line in its Redis versions table and supports it on the Assure and Operate tiers: Assure adds ACL, persistence and cluster reviews and 24/7 reactive support, and Operate adds 24/7 monitoring and a 15-minute P1 response. For a current line, fixes come from Redis's own releases, so there is no 8.0 patch for OSSeva to deliver. The patched builds OSSeva ships cover Redis 6.2 and 7.0 past community end of life. For 8.0 the route is the move to 8.2.
Redis extended supportWhat your auditor will say
Applicable security patches are expected on every system component, and a Redis instance that holds sessions or cached data is one. An 8.0 server that lacks the 5 May 2026 fixes needs a documented plan or a compensating control, such as the ACL restriction on RESTORE that the advisory describes.
Auditors ask for evidence that production systems receive security fixes. A line with no release since February, and none after 1 December, fails that test unless you can show the upgrade date.
When does Redis 8.0 reach end of life?
1 December 2026, according to redis.io's Redis Open Source version management page. endoflife.date shows the same date. 8.0 is a standard release, and its last release, 8.0.6, came out on 23 February 2026.
Is Redis 8.0 still supported?
On redis.io's list it is, until 1 December 2026. In practice no 8.0 release has come since 8.0.6 on 23 February 2026, while 8.2, 8.4 and 8.6 each had security releases on 5 May and 26 October 2026.
Does Redis still patch 8.0?
Not in the releases checked on 11 November 2026. The last 8.0 release is 8.0.6, and the 5 May 2026 security fixes shipped in 8.2.6, 8.4.3, 8.6.3, 7.2.14 and 7.4.9 only.
Is Redis 8.0 affected by the May 2026 CVEs?
Redis's advisories say CVE-2026-25243 affects all Redis versions, CVE-2026-23631 all versions with Lua scripting and CVE-2026-23479 Redis 7.2 or newer. 8.0.6 falls inside each range, and each is fixed in 8.2.6, 8.4.3 and 8.6.3. All three need an authenticated client.
What should I upgrade Redis 8.0 to?
Redis 8.2, an extended release supported until 1 September 2030. 8.4, 8.6, 8.8 and 8.10 are standard releases with no end date yet, and each stops getting fixes six months after its successor ships.
Can I roll back from 8.2 to 8.0?
Possibly by data file, since 8.0, 8.2 and 8.4 all write RDB version 12 in Redis's source. A move to 8.6 or later writes version 13, and an older server refuses a newer file. Test a restore first and keep the 8.0 primary until you are sure.
Is Redis Software 8.0 the same as Redis 8.0?
No. Redis Software is Redis's commercial product with its own lifecycle page. Its 8.0 was released in October 2025 and is listed as supported until 31 July 2028. This page covers Redis Open Source 8.0.
Get a quote
Still running Redis 8.0?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?