Redis 7.4 end of life
Redis 7.4 is supported until 1 December 2029. redis.io lists it as an extended release, which receives security updates and critical bug fixes for five years. 7.4.0 shipped on 29 July 2024 and the latest release is 7.4.12, from 26 October 2026. 7.4 is the first Redis line under a choice of RSALv2 or SSPLv1 instead of BSD-3-Clause.
What now
Who provides Redis 7.4 security patches once community support ends?
Redis EOL: Extended Support for Redis 6 and 7- End of life
- 1 December 2029
- Released
- Jul 2024
- Final release
- 7.4.12 (latest, 26 October 2026)
- Successor
- Redis 8.2 (to 1 September 2030), or Valkey
Date published by Redis Open Source version management. We do not publish a lifecycle date we cannot source. Dates checked on redis.io and endoflife.date on 20 October 2026.
Last reviewed
Redis versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Redis 8.0 | 2 May 2025 | 1 December 2026 | Approaching |
| Redis 7.4 (this page) | 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 2029
- Nothing yet. Redis keeps shipping security releases on 7.4. 7.4.9, in May 2026, fixed CVE-2026-23479, CVE-2026-25243 and CVE-2026-23631, each of which the release notes say may lead to remote code execution.
- On 1 December 2029, security updates and critical bug fixes end for 7.4, on the same day as 7.2.
- The licence does not revert. The 7.4 licence file offers RSALv2 or SSPLv1, and Redis 7.2 remains the last BSD-3-Clause line.
What actually breaks in the upgrade
Stay current on 7.4.x
Supported does not mean patched. A 7.4 server below 7.4.9 is missing fixes for three issues rated as possible remote code execution, and 7.4.11 added fixes for a use-after-free and an ACL key permission bypass.
Check persistence before a move to Valkey
The 7.4.0 release notes list RDB file format changes for hash field expiration. Valkey was forked from Redis before the licence change, so confirm that your Valkey target loads 7.4 snapshots, or plan a migration that copies the data, before you commit.
Skip 8.0
redis.io lists Redis 8.0 as a standard release ending on 1 December 2026. If Redis 8 is the target, use 8.2, an extended release supported to 1 September 2030.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Stay on 7.4 and keep patching | Upstream 7.4.x security releases to 1 December 2029. | A routine upgrade with each release | Engineering time | Fine for now, if each security release is applied. |
| Upgrade to Redis 8.2 | A major version upgrade on Redis's current licence terms. | Scales with client and test coverage | Engineering time and legal review | Supported to September 2030. |
| Move to Valkey | A BSD-3-Clause fork with its own release line. | Scales with client and test coverage | Engineering time | Returns to a permissive licence. Test persistence, clients and modules first. |
What OSSeva does for Redis 7.4
Assessed case by case
Redis 7.4 is not in OSSeva's Redis versions table, which lists the BSD-3-Clause lines 6.2, 7.0 and 7.2 alongside Valkey 7.2, 8.x and 9.x. For a 7.4 estate, OSSeva's route is a planned move to Valkey, which is covered; until then, 7.4 stays on Redis's own releases, which continue to 1 December 2029. Each case is assessed before quoting.
Redis extended supportWhat your auditor will say
The data store is a system component in its own right. An unsupported version with no patch source is a finding; a documented third-party patch stream is the usual remediation.
Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.
For EU financial entities, the ICT risk and third-party provisions apply when a critical service depends on software with no support arrangement in place.
What is the Redis 7.4 end of life date?
1 December 2029, according to redis.io. Redis 7.2 ends on the same date.
Is Redis 7.4 still supported?
Yes. It is an extended release with security updates and critical bug fixes until 1 December 2029. The latest is 7.4.12, from 26 October 2026.
What licence is Redis 7.4 under?
A choice of RSALv2 or SSPLv1, set out in the 7.4 licence file. Redis 7.2 and earlier are BSD-3-Clause.
What should I upgrade Redis 7.4 to?
Redis 8.2, an extended release supported to 1 September 2030, or Valkey if you want a BSD-3-Clause licence. Avoid 8.0, which ends on 1 December 2026.
Can Valkey read Redis 7.4 data files?
Check before relying on it. Redis 7.4.0 changed the RDB format for hash field expiration, and Valkey was forked from Redis before 7.4.
Get a quote
Still running Redis 7.4?
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?