Redis 6.2 end of life
Redis Open Source 6.2 reaches end of life on 1 April 2027, per the version management page on redis.io. It still gets fixes until then; the latest is 6.2.24, released on 17 August 2026. Redis Software 6.2, the commercial product, reached end of life on 28 February 2025. OSSeva ships patched Redis 6.2 builds past April 2027.
What now
Which vendors provide Redis 6.2 security patches after 1 April 2027?
Redis EOL: Extended Support for Redis 6 and 7- End of life
- 1 April 2027
- Released
- Feb 2021
- Final release
- 6.2.24 (latest, 17 August 2026)
- Successor
- Redis 7.2, 7.4 or 8.x, 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 | 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 (this page) | 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 April 2027
- Security and critical bug fixes on the 6.2 line after 1 April 2027. Recent examples include CVE-2025-49844, an authenticated remote code execution flaw scored 9.9 by NVD, fixed on 6.2 in 6.2.20.
- Nothing about the licence. Redis 7.2 and earlier stay under BSD-3-Clause; only the fix supply stops.
- Standard support on Amazon ElastiCache. Redis OSS 6 moves to ElastiCache Extended Support from 1 February 2027, billed as a premium on the on-demand node price that doubles in the third year.
What actually breaks in the upgrade
The licence depends on the target
Redis 7.2 and earlier are BSD-3-Clause. Redis 7.4 moved to a dual RSALv2 or SSPLv1 licence, and Redis 8 added AGPLv3 as a third option. Settle the licence question with legal before the engineering work starts, because it narrows the targets.
Pick the landing line by its date
redis.io lists end of life on 1 December 2029 for both 7.2 and 7.4, and 1 September 2030 for 8.2. Redis 8.0 ends on 1 December 2026, which makes it a poor target for a move off 6.2.
Valkey is the permissive route past 7.2
Teams that need a BSD-3-Clause licence beyond the 7.2 line look at Valkey, which is licensed BSD-3-Clause. Test clients, modules and persistence settings against it as you would any major upgrade.
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 7.2 | The last BSD-3-Clause Redis line, supported to 1 December 2029. | Scales with client and test coverage | Engineering time | The simplest move when the licence has to stay permissive. |
| Upgrade to Redis 8.x | Current Redis under RSALv2, SSPLv1 or AGPLv3. | Scales with client and test coverage | Engineering time plus licence review | The longest runway if one of the three licences works for you. 8.2 runs to September 2030. |
| Move to Valkey | A BSD-3-Clause licensed alternative. | Scales with client and test coverage | Engineering time | Right when permissive licensing matters more than staying on Redis itself. |
| OSSeva patched builds on 6.2 | Signed 6.2 builds under BSD-3-Clause, continuing after April 2027. | Scales with the number of nodes and clients | Subscription | Removes the deadline from the migration plan without changing licence or supplier. |
What OSSeva does for Redis 6.2
OSSeva patches this line
OSSeva ships patched, signed Redis 6.2 builds under the original BSD-3-Clause licence. Assure and Operate cover 6.2 today, and Patch subscriptions carry CVE fixes on 6.2 past 1 April 2027 with no change of supplier or licence.
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.
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.
When does Redis 6.2 reach end of life?
Redis Open Source 6.2 reaches end of life on 1 April 2027, per redis.io. Redis Software 6.2, the commercial product, reached end of life on 28 February 2025.
Is Redis 6.2 still getting patches?
Yes, until 1 April 2027. The latest release is 6.2.24, published on 17 August 2026.
Is Redis 6.2 open source?
Yes. Redis 7.2 and earlier remain under BSD-3-Clause. Redis 7.4 moved to RSALv2 or SSPLv1, and Redis 8 added AGPLv3.
Can I keep Redis 6.2 patched after April 2027?
Yes. OSSeva ships patched, signed Redis 6.2 builds under BSD-3-Clause, and they continue after the community end-of-life date.
Get a quote
Still running Redis 6.2?
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?