[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fodlxlOb2PXsSrPnWH_Qlnd-EgpJbeE_EWUMi5Wv-5Wk":3},{"product":4,"cycleMajor":14,"releases":15,"cves":26,"nextMajor":42,"indexable":43},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":11,"official_url":9,"synced_at":12,"created_at":13},"fa665824-5ef1-4f4a-a3d3-80e2b74b3986","redis","Redis","database",null,"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.\n\nThe 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.\n\nWhen 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.","https:\u002F\u002Fcdn.simpleicons.org\u002Fredis","2026-10-07T02:00:11.306+00:00","2026-05-30T16:23:55.974439+00:00","5",[16],{"id":17,"product_id":5,"cycle":18,"release_date":19,"eol":20,"eol_boolean":9,"latest":21,"latest_release_date":22,"lts":23,"support":24,"created_at":25},"68aea5c5-0a3d-4f61-bdf9-8f4f6994b93b","5.0","2018-10-17","2022-04-27","5.0.14","2021-10-04",false,"2020-04-30","2026-05-30T16:34:34.181331+00:00",[27,35],{"cveId":28,"releaseId":17,"cycle":18,"description":29,"severity":30,"cvssScore":31,"epssScore":32,"inKev":23,"publishedAt":33,"url":34},"CVE-2026-25243","Redis is an in-memory data structure store. In versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may lead to remote code execution. A workaround is to restrict access to the RESTORE command with ACL rules. This is patched in version 8.6.3.","HIGH",8.8,0.03663,"2026-05-05T17:17:03.667+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-25243",{"cveId":36,"releaseId":17,"cycle":18,"description":37,"severity":30,"cvssScore":38,"epssScore":39,"inKev":23,"publishedAt":40,"url":41},"CVE-2026-23631","Redis is an in-memory data structure store. In all versions of redis-server with Lua scripting, an authenticated attacker can exploit the master-replica synchronization mechanism to trigger a use-after-free on replicas where replica-read-only is disabled or can be disabled, which may lead to remote code execution. A workaround is to prevent users from executing Lua scripts or avoid using replicas where replica-read-only is disabled. This is patched in version 8.6.3.",8.1,0.02805,"2026-05-05T17:17:03.503+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2026-23631","6",true]