CISA list

Redis versions

Redis: update to 8.10.3, 8.8.4, 8.6.8, 8.4.8, 8.2.11, 8.0.6, 7.4.12, 7.2.17 or 6.2.24. 7.0 and 6.0 and older have reached end of life in the lifecycle data.

Data: .

Which Redis branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are counted at the end of the page.

Which Redis branch to run
BranchStatusNewest safe releaseUpgrade to
8.10Bug and security fixes, no end date announced8.10.38.10.3 (this branch)
8.8Security fixes only, no end date announced8.8.48.8.4 (this branch)
8.62 CVE records that this page readsSecurity fixes only, no end date announced8.6.88.6.8 (this branch)
8.4Security fixes only, no end date announced8.4.88.4.8 (this branch)
8.25 CVE records that this page readsSecurity fixes only until 1 September 20308.2.118.2.11 (this branch)
8.0Security fixes only until 1 December 20268.0.68.0.6 (this branch)
7.41 CVE record that this page readsSecurity fixes only until 1 December 20297.4.127.4.12 (this branch)
7.22 CVE records that this page readsSecurity fixes only until 1 December 20297.2.177.2.17 (this branch)
7.011 CVE records that this page readsEnded on 29 July 2024None, the branch has ended7.2.17 (move to 7.2)
6.215 CVE records that this page readsSecurity fixes only until 1 April 20276.2.246.2.24 (this branch)
6.013 CVE records that this page readsEnded on 31 May 2022None, the branch has ended6.2.24 (move to 6.2)
5.06 CVE records that this page readsEnded on 27 April 2022None, the branch has ended6.2.24 (move to 6.2)

Exploited, or likely to be

CVE records for Redis that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the releases that fix each where the record names them. 5 of the 6 records shown name one.

Exploited, or likely to be
RecordSigns of exploitationFixed in
CVE-2025-32023Redis allows out of bounds writes in hyperloglog commands leading to RCE7.0 High · published 7 July 2025Exploit-DB entryThis page does not place it on a branch.
CVE-2025-49844Redis Lua Use-After-Free may lead to remote code execution10.0 Critical · published 3 October 2025EPSS 0.50 or moreFixed in 8.2.2
CVE-2023-36824Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis7.4 High · published 11 July 2023EPSS 0.50 or moreFixed in 7.0.12
CVE-2023-22458Integer overflow in multiple Redis commands can lead to denial-of-service5.5 Medium · published 20 January 2023EPSS 0.50 or moreFixed in 7.0.8, 6.2.9
CVE-2022-36021Redis string pattern matching can be abused to achieve Denial of Service5.5 Medium · published 1 March 2023EPSS 0.50 or moreFixed in 7.0.9, 6.2.11, 6.0.18
CVE-2023-28425Specially crafted MSETNX command can lead to denial-of-service5.5 Medium · published 20 March 2023EPSS 0.50 or moreFixed in 7.0.10

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 45 CVE records that GitHub's CVE Numbering Authority published and that name Redis. The fixes are from the 28 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here. Some of these branches are still named by records published after they ended; the page of each says how many.

Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.

17 records are not placed on a branch, so no branch or release row counts them: CVE-2021-32626, CVE-2021-32672, CVE-2021-32761, CVE-2021-41099, CVE-2022-24735, CVE-2022-24736, CVE-2023-41053, CVE-2023-45145, CVE-2024-31227 and CVE-2024-31228 and 7 others.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)