CVE-2026-56684

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.

Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.

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.

Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.

Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.

These are all security issues fixed in the valkey-9.1.1-1.1 package on the GA media of openSUSE Tumbleweed.

This update for valkey fixes the following issues:

Update to version 8.0.10.

• CVE-2026-56684: RCE via CLIENT KILL due to use-after-free in TLS connection handling (bsc#1272443).
• CVE-2026-63639: RCE via corrupt stream RDB files due to use-after-free when loading a stream consumer group from RDB (bsc#1272442).

This update for valkey fixes the following issues:

• CVE-2026-56684: use-after-free in TLS connection handling that could allow an authenticated client to achieve remote code execution using CLIENT KILL (bsc#1272443).
• CVE-2026-63639: corrupt stream RDB files containing a shared NACK across consumers can lead to remote code execution (bsc#1272442).

Changes for valkey:

• Update to 8.0.10.

This update for valkey fixes the following issues

• CVE-2026-56684: use-after-free in TLS connection handling (bsc#1272443).
• CVE-2026-63639: RCE via corrupt stream RDB files containing a shared NACK across consumers (bsc#1272442).

Changes for valkey:

• Update to 8.0.10.

Madelyn Olson discovered that Valkey incorrectly handled TLS connections under certain conditions. A remote attacker could possibly use this issue to cause Valkey to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-56684)

It was discovered that Valkey incorrectly handled certain stream RDB payloads when executing the RESTORE command. An authenticated remote attacker could possibly use this issue to cause Valkey to crash, resulting in a denial of service, or execute arbitrary code. (CVE-2026-63639)

It was discovered that Valkey incorrectly handled cluster slot migration operations. A remote attacker could possibly use this issue to cause Valkey to crash, resulting in a denial of service. This issue was only addressed in Ubuntu 26.04 LTS. (CVE-2026-85522)