Redis 8.10.2 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• redis/redis#15673 Commands queued in a transaction could still access keys whose ACL permissions were revoked before the transaction was executed
• redis/redis#15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus
• TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload
• RedisSearch: KNN queries on indexes with very long vector field names could cause the server to crash
• Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : 7C8CEBD50347EAA1D9E784DA842ED47A4F33394637835531D6614777B950EE85
Path : D:\a\redis-windows\redis-windows\Redis-8.10.2-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : AA43EDCF35773607A29D3D5A9F6FD6825D2C8177E6E83CA91F91866A9329DA27
Path : D:\a\redis-windows\redis-windows\Redis-8.10.2-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 6DE5CC7F5ADBF97B5928B13766383D4AD424626EF3D8B313FFFF12D820EC6FC1
Path : D:\a\redis-windows\redis-windows\Redis-8.10.2-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : C9E9D4DC5347620F7514FCE4F2999802F1F984F9788C5FAC1A2710295D8F86C4
Path : D:\a\redis-windows\redis-windows\Redis-8.10.2-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/35294974076

Redis 8.8.3 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• redis/redis#15673 Commands queued in a transaction could still access keys whose ACL permissions were revoked before the transaction was executed
• redis/redis#15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus
• TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload
• Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : C2EBC76C007A12C96D7DD64E252A194D9E6A06FE801DFB834CA071314FD662E7
Path : D:\a\redis-windows\redis-windows\Redis-8.8.3-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : 0F842DAFFB25797AD8717A19BC47D35FB04A3A94FE547E6FAC8C17EED3DB57FB
Path : D:\a\redis-windows\redis-windows\Redis-8.8.3-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : BB19F830CA5BF62718E81F230833F968B90ECFD675557CAF3C1478C4E65BD98C
Path : D:\a\redis-windows\redis-windows\Redis-8.8.3-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : CE926F3C17728BD5250EFACFDA27ABACFE8AA13FB9F1B7545E974A3221F51467
Path : D:\a\redis-windows\redis-windows\Redis-8.8.3-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/35414969678

Redis 8.6.7 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• redis/redis#15673 Commands queued in a transaction could still access keys whose ACL permissions were revoked before the transaction was executed
• redis/redis#15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus
• TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload
• Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : 08286EB017217FB18AF0E70454099133AE24E3A90D9D837F67D93286F7F441D0
Path : D:\a\redis-windows\redis-windows\Redis-8.6.7-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : 32A5228089FEBCDC463689C6C4EF64DA36D602A60434B240166996132849CA4C
Path : D:\a\redis-windows\redis-windows\Redis-8.6.7-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 69574FF3E47B472D2F6F933751DBA9B60F93069F0DFA3147FC90054017CE1939
Path : D:\a\redis-windows\redis-windows\Redis-8.6.7-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : 71D663D34314BAF942D8F50C7344300F6BA2584F19E1316876D30C124572B182
Path : D:\a\redis-windows\redis-windows\Redis-8.6.7-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/35414959798

Redis 8.4.7 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• redis/redis#15673 Commands queued in a transaction could still access keys whose ACL permissions were revoked before the transaction was executed
• redis/redis#15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus
• TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload
• Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : 3A42871A878976EA372DB25F8F04190E82403854255A44AA39C349DCEEC6AEA3
Path : D:\a\redis-windows\redis-windows\Redis-8.4.7-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : 915CED5794DDC854D5A4184FFA37B2FCACAECED5D1DE3B95037A59D09EE8FE34
Path : D:\a\redis-windows\redis-windows\Redis-8.4.7-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 8BC1C546BB7B6508FD4DBE64FABBF63DBAAF04EFECA8A6397856DA74C80757DA
Path : D:\a\redis-windows\redis-windows\Redis-8.4.7-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : 142D38B2A1A89C1E2A59F4809D6775E1E41DC37520D0CFEE4DF618AD1499781A
Path : D:\a\redis-windows\redis-windows\Redis-8.4.7-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/35414948036

Redis 8.2.10 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• redis/redis#15722 The cluster bus protocol has no authentication of its own unless tls-cluster is enabled, so any host able to reach a node's bus port could join the cluster and threaten it. A cluster node now warns at startup when its bus port is left unauthenticated, and the new cluster-bus-port-protected-mode option (default no) makes refusing to run in that state an explicit choice: set it to yes and the node starts only when tls-cluster authenticates the bus
• TimeSeries: Prevented Redis from crashing when adding samples to a compressed Time Series key restored from a malformed RDB payload
• Vector Sets: Deeply nested JSON used in Vector Set queries could cause the server to crash

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : 281F180EABA420F43EB18D655197D55BF804EB692BC55209264BFB284DA3850F
Path : D:\a\redis-windows\redis-windows\Redis-8.2.10-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : 10A009E4F05C356398C9FC7853E0D47E99D4E2AD666764FF2507C478F89750A0
Path : D:\a\redis-windows\redis-windows\Redis-8.2.10-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 92D9BDDE87ED52BF859A677E5197D8AC855BA78D9940D457881723AE960DF429
Path : D:\a\redis-windows\redis-windows\Redis-8.2.10-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : F80DB57BAE0089887801375BA4DC40F705AB1D49FDE7769E85A64936A8BBE557
Path : D:\a\redis-windows\redis-windows\Redis-8.2.10-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/35414937094

Redis 8.10.1 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• (CVE-2026-62356) Miscalculated buffer size in CMSketch RDB loading may lead to heap OOB write
• Out-of-bounds access in TopK heap cleanup path (MOD-15410)
• Use-after-free in the TLS pending-data list when a command closes another pending connection
• A malicious RDB payload with an out-of-range SLOT_INFO slot id causes memory corruption during RDB loading, which may lead to Remote Code Execution
• Vector Sets: missing node level validation when loading a vector set from RDB may lead to out-of-bounds access
• Vector Sets: use-after-free when VREM mutates the HNSW graph while background VSIM threads are still running
• Vector Sets: a negative hnsw_search() return was treated as a huge unsigned count, reading past the end of the result arrays
• TLS client certificate authentication bypass: a Common Name containing an embedded NUL byte was truncated, allowing a client to authenticate as another (possibly privileged) ACL user
• redis/redis#15594 Use-after-free in the blocked-client list when reprocessing a command evicts another client blocked on the same key

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : 4E8F2F956ED92FEADF3F64B4E137ED34026438821E692E7AE22C9BBA5976607A
Path : D:\a\redis-windows\redis-windows\Redis-8.10.1-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : 8D7710C858EB9EF24685D040272FA42F6B045906CBAB14DC635697A20303AF1B
Path : D:\a\redis-windows\redis-windows\Redis-8.10.1-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 5532F2CC38A0185556B648D25A0C2FF1CC58029F37FD76ECEB38736976DCB056
Path : D:\a\redis-windows\redis-windows\Redis-8.10.1-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : E70EEA271F2B8D4BC113FE4A95331BEAA2CD4B22C4ED07C93C54E342CB1788DB
Path : D:\a\redis-windows\redis-windows\Redis-8.10.1-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/32091074661

Redis 8.8.2 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• (CVE-2026-62356) Miscalculated buffer size in CMSketch RDB loading may lead to heap OOB write
• Out-of-bounds access in TopK heap cleanup path (MOD-15410)
• Use-after-free in the TLS pending-data list when a command closes another pending connection
• redis/redis#15478 ACL key permission bypass in SORT, GEORADIUS/GEORADIUSBYMEMBER and XREAD/XREADGROUP: the keys validated by ACL could differ from the keys the command actually accesses
• A malicious RDB payload with an out-of-range SLOT_INFO slot id causes memory corruption during RDB loading, which may lead to Remote Code Execution
• Vector Sets: missing node level validation when loading a vector set from RDB may lead to out-of-bounds access
• Vector Sets: use-after-free when VREM mutates the HNSW graph while background VSIM threads are still running
• Vector Sets: a negative hnsw_search() return was treated as a huge unsigned count, reading past the end of the result arrays
• TLS client certificate authentication bypass: a Common Name containing an embedded NUL byte was truncated, allowing a client to authenticate as another (possibly privileged) ACL user
• redis/redis#15594 Use-after-free in the blocked-client list when reprocessing a command evicts another client blocked on the same key

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : 7E79469CB8644A5C1CC466625CAD5B4A68F34AF207CA2C6779B3128E010CB453
Path : D:\a\redis-windows\redis-windows\Redis-8.8.2-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : 3B86882C4B8358DA5AFCF36029F4B79CF3748C5C393C624B6CB00152095182E1
Path : D:\a\redis-windows\redis-windows\Redis-8.8.2-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 9E603AD77224B30AC090BA963735B6A014373F6510001F0D9AF3B8C3415B9A17
Path : D:\a\redis-windows\redis-windows\Redis-8.8.2-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : EC6C628FCB0616B42831EAFAEF31069A5D5767D9480FDCD2724D637F0B1A8CB8
Path : D:\a\redis-windows\redis-windows\Redis-8.8.2-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/32123662518

Redis 8.6.6 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• (CVE-2026-62356) Miscalculated buffer size in CMSketch RDB loading may lead to heap OOB write
• Out-of-bounds access in TopK heap cleanup path (MOD-15410)
• Use-after-free in the TLS pending-data list when a command closes another pending connection
• redis/redis#15478 ACL key permission bypass in SORT, GEORADIUS/GEORADIUSBYMEMBER and XREAD/XREADGROUP: the keys validated by ACL could differ from the keys the command actually accesses
• A malicious RDB payload with an out-of-range SLOT_INFO slot id causes memory corruption during RDB loading, which may lead to Remote Code Execution
• Vector Sets: missing node level validation when loading a vector set from RDB may lead to out-of-bounds access
• Vector Sets: use-after-free when VREM mutates the HNSW graph while background VSIM threads are still running
• Vector Sets: a negative hnsw_search() return was treated as a huge unsigned count, reading past the end of the result arrays
• TLS client certificate authentication bypass: a Common Name containing an embedded NUL byte was truncated, allowing a client to authenticate as another (possibly privileged) ACL user
• redis/redis#15594 Use-after-free in the blocked-client list when reprocessing a command evicts another client blocked on the same key

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : A3800521899E594E4E5634A94771ABDEB966FEC18AA46E731B90BFD11735DC8B
Path : D:\a\redis-windows\redis-windows\Redis-8.6.6-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : C4DAF0A226BECE41CA9E3AE94917DA39846AC9319FFE11329AF776186F64FC89
Path : D:\a\redis-windows\redis-windows\Redis-8.6.6-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 1A83EBBC52F302FB9A2DE2764BB96C1DA9075F7988C9F9E9E1450EDB759D8658
Path : D:\a\redis-windows\redis-windows\Redis-8.6.6-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : 2C2FCD70A6BAB6E84DAF2D27FF73C29AA37AC0129FD4148943ADBFA338EF5301
Path : D:\a\redis-windows\redis-windows\Redis-8.6.6-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/32123644394

Redis 8.4.6 for Windows

Update urgency: SECURITY: There are security fixes in the release.

Security fixes

• (CVE-2026-62356) Miscalculated buffer size in CMSketch RDB loading may lead to heap OOB write
• Out-of-bounds access in TopK heap cleanup path (MOD-15410)
• Use-after-free in the TLS pending-data list when a command closes another pending connection
• redis/redis#15478 ACL key permission bypass in SORT, GEORADIUS/GEORADIUSBYMEMBER and XREAD/XREADGROUP: the keys validated by ACL could differ from the keys the command actually accesses
• redis/redis#14847 Out-of-bounds argv access during key extraction when checking ACL permissions of a KEYNUM keyspec command (e.g. EVAL) with wrong arity
• A malicious RDB payload with an out-of-range SLOT_INFO slot id causes memory corruption during RDB loading, which may lead to Remote Code Execution
• Vector Sets: missing node level validation when loading a vector set from RDB may lead to out-of-bounds access
• Vector Sets: use-after-free when VREM mutates the HNSW graph while background VSIM threads are still running
• Vector Sets: a negative hnsw_search() return was treated as a huge unsigned count, reading past the end of the result arrays
• redis/redis#15594 Use-after-free in the blocked-client list when reprocessing a command evicts another client blocked on the same key

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : 3F3714E0B005FDBFDA358A8CCD9B7E9C43A16566E53A032A3C8DBA04BF7B3782
Path : D:\a\redis-windows\redis-windows\Redis-8.4.6-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : C6F0FD7C4DD07EC7D621D3D8E03870CBA6539980E2ACA41A3A32A44C2B1788D5
Path : D:\a\redis-windows\redis-windows\Redis-8.4.6-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 58B45CB89FA2CCD99F9814ADB77B6C459A794F78F89A38335205829DB6990B0F
Path : D:\a\redis-windows\redis-windows\Redis-8.4.6-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : DCCC420ECF0EF66C72F9CB2A36DC142637F17F17736651BA6E6B9B159CDC0EC2
Path : D:\a\redis-windows\redis-windows\Redis-8.4.6-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/32123619724

Redis 8.2.9 for Windows

Security fixes

• (CVE-2026-62356) Miscalculated buffer size in CMSketch RDB loading may lead to heap OOB write
• Out-of-bounds access in TopK heap cleanup path (MOD-15410)
• Use-after-free in the TLS pending-data list when a command closes another pending connection
• redis/redis#15478 ACL key permission bypass in SORT, GEORADIUS/GEORADIUSBYMEMBER and XREAD/XREADGROUP: the keys validated by ACL could differ from the keys the command actually accesses
• redis/redis#14847 Out-of-bounds argv access during key extraction when checking ACL permissions of a KEYNUM keyspec command (e.g. EVAL) with wrong arity
• A malicious RDB payload with an out-of-range SLOT_INFO slot id causes memory corruption during RDB loading, which may lead to Remote Code Execution
• Vector Sets: missing node level validation when loading a vector set from RDB may lead to out-of-bounds access
• Vector Sets: use-after-free when VREM mutates the HNSW graph while background VSIM threads are still running
• Vector Sets: a negative hnsw_search() return was treated as a huge unsigned count, reading past the end of the result arrays
• redis/redis#15594 Use-after-free in the blocked-client list when reprocessing a command evicts another client blocked on the same key

Hashes

MSYS2 Builds Hashes

Algorithm : SHA256
Hash : DCFF676E861A4AE0A9854556239398E77A7469C9379AF64A4A76798D166D1AA0
Path : D:\a\redis-windows\redis-windows\Redis-8.2.9-Windows-x64-msys2.zip

Algorithm : SHA256
Hash : 504EF26F7C78C994254779FC89D9A4D83D6E065E4F1C37528810CF0044483F4C
Path : D:\a\redis-windows\redis-windows\Redis-8.2.9-Windows-x64-msys2-with-Service.zip

Cygwin Builds Hashes

Algorithm : SHA256
Hash : 894F381F544FC98977F37D46C3CD713FF1C2778DE1FC77E0300FD80AFA8496DD
Path : D:\a\redis-windows\redis-windows\Redis-8.2.9-Windows-x64-cygwin.zip

Algorithm : SHA256
Hash : 55021E97108BA2C19C58083FC9A021B0C25923F310BDDD118D16A998ED8DDAF3
Path : D:\a\redis-windows\redis-windows\Redis-8.2.9-Windows-x64-cygwin-with-Service.zip

From workflow: https://github.com/redis-windows/redis-windows/actions/runs/32123592219