CVE-2026-66373

Redis is an advanced key-value store. It is often referred to as a dattructure server since keys can contain strings, hashes ,lists, sets anorted sets.

Security Fix(es):

Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243.(CVE-2026-66373)

Valkey is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Valkey works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Valkey also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Valkey behave like a cache. You can use Valkey from most programming languages also.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)

• valkey: Valkey: Remote code execution via use-after-free in stream deserialization (CVE-2026-63639)

• valkey: Valkey: Remote code execution via TLS pending-data processing use-after-free (CVE-2026-56684)

Bug Fix(es) and Enhancement(s):

• [Tracker] Rebase valkey to 8.0.10 (JIRA:Rocky Linux-216776)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Valkey is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Valkey works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Valkey also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Valkey behave like a cache. You can use Valkey from most programming languages also.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)

• valkey: Valkey: Remote code execution via use-after-free in stream deserialization (CVE-2026-63639)

• valkey: Valkey: Remote code execution via TLS pending-data processing use-after-free (CVE-2026-56684)

Bug Fix(es) and Enhancement(s):

• [Tracker] Rebase valkey to 8.0.10 (JIRA:Rocky Linux-216778)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)

• redis: Redis: Arbitrary code execution via TLS pending-data list use-after-free (CVE-2026-81934)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)

• redis: Redis: Arbitrary code execution via TLS pending-data list use-after-free (CVE-2026-81934)

Bug Fix(es) and Enhancement(s):

• segfault because of Unsupported system page size (jemalloc) (JIRA:Rocky Linux-180910)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)

• redis: Redis: Denial of Service via Out-of-Bounds Read in Cluster Bus (CVE-2026-72568)

• redis: Redis: Arbitrary code execution via TLS pending-data list use-after-free (CVE-2026-81934)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243.

Valkey is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Valkey works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Valkey also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Valkey behave like a cache. You can use Valkey from most programming languages also.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)
• valkey: Valkey: Remote code execution via use-after-free in stream deserialization (CVE-2026-63639)
• valkey: Valkey: Remote code execution via TLS pending-data processing use-after-free (CVE-2026-56684)

Bug Fix(es) and Enhancement(s):

• [Tracker] Rebase valkey to 8.0.10 (JIRA:AlmaLinux-216776)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Valkey is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Valkey works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Valkey also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Valkey behave like a cache. You can use Valkey from most programming languages also.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)
• valkey: Valkey: Remote code execution via use-after-free in stream deserialization (CVE-2026-63639)
• valkey: Valkey: Remote code execution via TLS pending-data processing use-after-free (CVE-2026-56684)

Bug Fix(es) and Enhancement(s):

• [Tracker] Rebase valkey to 8.0.10 (JIRA:AlmaLinux-216778)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)
• redis: Redis: Arbitrary code execution via TLS pending-data list use-after-free (CVE-2026-81934)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log.

Security Fix(es):

• redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)
• redis: Redis: Arbitrary code execution via TLS pending-data list use-after-free (CVE-2026-81934)

Bug Fix(es) and Enhancement(s):

• segfault because of Unsupported system page size (jemalloc) (JIRA:AlmaLinux-180910)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243.

• SECURITY UPDATE: Memory exhaustion via unauthenticated client output buffer
  • debian/patches/0016-CVE-2025-21605.patch: cap the output buffer of unauthenticated clients in checkClientOutputBufferLimits() in src/networking.c, so a client that never reads its NOAUTH replies cannot grow the buffer without bound. Backport of upstream redis commit 5e93f9cb9 (6.2.18) as shipped by Debian for bullseye in 5:6.0.16-1+deb11u9 (DLA-4162-1), adapted to 5.0 by spelling the condition as server.requirepass && !c->authenticated, since 5.0 predates the ACL subsystem and has no authRequired() helper.
  • CVE-2025-21605
• SECURITY UPDATE: Client starvation via repeated accept() errors
  • debian/patches/0017-CVE-2025-48367.patch: add anetAcceptFailureNeedsRetry() to src/anet.c and retry the accept loop in acceptTcpHandler()/acceptUnixHandler() in src/networking.c and clusterAcceptHandler() in src/cluster.c, so a connection that fails at accept() time no longer aborts the whole batch and starves other pending clients. Backport of upstream redis commit 0fe674359 (6.2.19) as shipped by Debian for bullseye in 5:6.0.16-1+deb11u9 (DLA-4240-1); the acceptTLSHandler() hunk is dropped because 5.0 has no TLS support.
  • CVE-2025-48367
• SECURITY UPDATE: Double free via stream RDB payload with a shared NACK
  • debian/patches/0018-CVE-2026-66373.patch: reject a stream payload whose consumer PELs reference the same global-PEL NACK twice, in rdbLoadObject() in src/rdb.c, so RESTORE can no longer build two consumers sharing one streamNACK and have XGROUP DELCONSUMER free it twice. Backport of upstream redis commit 41a958720 (6.2.23) as shipped by Debian for bullseye and bookworm in 5:6.0.16-1+deb11u9 and 5:7.0.15-1~deb12u9 (DLA-4722-1), taken verbatim in the Debian form that uses rdbExitReportCorruptRDB(). Note this CVE exists because of an incomplete fix for CVE-2026-25243, which is a separate change and is not addressed here.
  • CVE-2026-66373

• CVE-2026-66373: reject corrupt stream RDB/RESTORE payloads in which the same global PEL NACK is claimed by more than one consumer, which led to a double free in rdbLoadObject stream consumer PEL loading

• CVE-2026-66373: fix double free by rejecting corrupt stream RDB payloads in which one global PEL NACK is claimed by more than one consumer

This update for redis7 fixes the following issue:

• CVE-2026-66373: remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer (bsc#1273162).

This update for redis fixes the following issue:

• CVE-2026-66373: remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer (bsc#1273162).

This update for redis fixes the following issue:

• CVE-2026-66373: remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer (bsc#1273162).

This update for redis7 fixes the following issue:

• CVE-2026-66373: remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer (bsc#1273162).