{
"id": "rs-8-0-10-76",
"title": "Redis Software release notes 8.0.10-76 (February 2026)",
"url": "https://redis.io/docs/latest/operate/rs/release-notes/rs-8-0-releases/rs-8-0-10-76/",
"summary": "Bug fix for database failover error after node crashes and recovery. `filter_node_wd_health_metrics` policy, enabled by default to filter new node watchdog health metrics. Internal fixes and improvements.",
"tags": [
"docs",
"operate",
"rs"
],
"last_updated": "2026-04-01T08:10:08-05:00",
"page_type": "content",
"content_hash": "a48d820bb31572ba0baf1bcdd511c58e6aabc8cd2053a20879fbac1bb1d46c30",
"sections": [
{
"id": "overview",
"title": "Overview",
"role": "overview",
"text": "This is a maintenance release for [Redis Software version 8.0.10](https://redis.io/downloads/#Redis_Software)."
},
{
"id": "highlights",
"title": "Highlights",
"role": "content",
"text": "This version offers:\n\n- Bug fix for database failover error after node crashes and recovery\n\n- `filter_node_wd_health_metrics` policy, enabled by default to filter new node watchdog health metrics\n\n- Internal fixes and improvements"
},
{
"id": "new-in-this-release",
"title": "New in this release",
"role": "content",
"text": ""
},
{
"id": "redis-database-versions",
"title": "Redis database versions",
"role": "content",
"text": "Redis Software version 8.0.10 includes the following Redis database versions: 8.4.0, 8.2.1, 8.0.2, 7.4.3, 7.2.7, and 6.2.13.\n\nThe [default Redis database version]() is 8.4."
},
{
"id": "redis-feature-sets",
"title": "Redis feature sets",
"role": "content",
"text": "Redis Software includes multiple feature sets, compatible with different Redis database versions.\n\nThe following table shows which Redis modules are compatible with each Redis database version included in this release.\n\n| Redis database version | Compatible Redis modules |\n|------------------------|--------------------------|\n| 8.4 | RediSearch 8.4
RedisJSON 8.4
RedisTimeSeries 8.4
RedisBloom 8.4
See [What's new in Redis 8.4]() and [Redis Open Source 8.4 release notes]() |\n| 8.2 | RediSearch 8.2
RedisJSON 8.2
RedisTimeSeries 8.2
RedisBloom 8.2
See [What's new in Redis 8.2]() and [Redis Open Source 8.2 release notes]() |\n| 8.0 | RediSearch 8.0
RedisJSON 8.0
RedisTimeSeries 8.0
RedisBloom 8.0
See [What's new in Redis 8.0]() and [Redis Open Source 8.0 release notes]() |\n| 7.4 | [RediSearch 2.10]()
[RedisJSON 2.8]()
[RedisTimeSeries 1.12]()
[RedisBloom 2.8]() |\n| 7.2 | [RediSearch 2.8]()
[RedisJSON 2.6]()
[RedisTimeSeries 1.10]()
[RedisBloom 2.6]() |\n| 6.2 | [RediSearch 2.6]()
[RedisJSON 2.4]()
[RedisTimeSeries 1.8]()
[RedisBloom 2.4]() |"
},
{
"id": "resolved-issues",
"title": "Resolved issues",
"role": "content",
"text": "- RS180524: Fixed an issue where database failover operations could enter a final error state after node crashes and recovery.\n\n- RS186040: Added a `filter_node_wd_health_metrics` policy and enabled it by default to filter new node watchdog health metrics."
},
{
"id": "version-changes",
"title": "Version changes",
"role": "compatibility",
"text": ""
},
{
"id": "breaking-changes",
"title": "Breaking changes",
"role": "content",
"text": "- Upgrading to this Redis Software version can cause LDAP authentication to fail with \"certificate signed by unknown authority\" errors if your cluster currently uses LDAP authentication. This issue will be fixed in a future maintenance release."
},
{
"id": "supported-platforms",
"title": "Supported platforms",
"role": "compatibility",
"text": "The following table provides a snapshot of supported platforms as of this Redis Software release. See the [supported platforms reference]() for more details about operating system compatibility.\n\n✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules.\n\n:warning: Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release.\n\n| Redis Software
major versions | 8.0 | 7.22 | 7.8 | 7.4 | 7.2 | 6.4 | 6.2 |\n|---------------------------------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|\n| **Release date** | Oct 2025 | May 2025 | Nov 2024 | Feb 2024 | Aug 2023 | Feb 2023 | Aug 2021 |\n| [**End-of-life date**]() | Determined after
next major release | Oct 2027 | May 2027 | Nov 2026 | Feb 2026 | Aug 2025 | Feb 2025 |\n| **Platforms** | | | | | | | |\n| RHEL 9 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | – | – | – |\n| RHEL 9
FIPS mode[5](#table-note-5) | ✅ | ✅ | ✅ | – | – | – | – |\n| RHEL 8 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |\n| RHEL 7 &
compatible distros[1](#table-note-1) | – | – | – | – | :warning: | :warning: | :warning: |\n| Ubuntu 22.04[2](#table-note-2) | ✅ | ✅ | ✅ | – | – | – | – |\n| Ubuntu 20.04[2](#table-note-2) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – |\n| Ubuntu 18.04[2](#table-note-2) | – | – | – | :warning: | :warning: | :warning: | :warning: |\n| Ubuntu 16.04[2](#table-note-2) | – | – | – | – | :warning: | :warning: | :warning: |\n| Amazon Linux 2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – |\n| Amazon Linux 1 | – | – | – | – | :warning: | :warning: | :warning: |\n| Kubernetes[3](#table-note-3) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |\n| Docker[4](#table-note-4) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |\n\n1. The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported.\n\n2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments.\n\n3. See the [Redis Enterprise for Kubernetes documentation]() for details about support per version and Kubernetes distribution.\n\n4. [Docker images]() of Redis Software are certified for development and testing only.\n\n5. Supported only if [FIPS was enabled during RHEL installation](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/security_hardening/switching-rhel-to-fips-mode_security-hardening#proc_installing-the-system-with-fips-mode-enabled_switching-rhel-to-fips-mode) to ensure FIPS compliance."
},
{
"id": "downloads",
"title": "Downloads",
"role": "content",
"text": "The following table shows the SHA256 checksums for the available packages:\n\n| Package | SHA256 checksum (8.0.10-76 February release) |\n|---------|---------------------------------------|\n| Ubuntu 20 | 11e1f537688f701d1c81f1932bea14f1f1613ff7e95539fb413f918d35e17685 |\n| Ubuntu 22 (amd64) | 3f416174d406153a0b3f03ab5bc02a4353aa3f2fd0550d9923518b48c8065ab0 |\n| Ubuntu 22 (arm64) | d58de57044463eadbf716945dcf56a71c4f0c6a63dd9a9cbc69f5729ad1bf03a |\n| Red Hat Enterprise Linux (RHEL) 8 | fecf9476f6a86130c3fdedaf2f8c4905e80f98f5ecb43c3a7ad2c7322730b5a9 |\n| Red Hat Enterprise Linux (RHEL) 9 (amd64) | 23c4aeb236237710de3aae5da15792022e260c53f381d9f5920c2a2f6bbbc18e |\n| Red Hat Enterprise Linux (RHEL) 9 (arm64) | 0c4c629f02c36cb222a732f141a15f3b0e7b634abc8d4839b7df4bdb1d1953e8 |\n| Amazon Linux 2 | 90835d32ff0f982ddee9ff53b4794d984711afc4c01f60521adfe3c23cd0dbbf |"
},
{
"id": "known-issues",
"title": "Known issues",
"role": "content",
"text": "- RS155734: Endpoint availability metrics do not work as expected due to a calculation error."
},
{
"id": "known-limitations",
"title": "Known limitations",
"role": "content",
"text": "#### Trim ACKED not supported for Active-Active 8.4 databases\n\nFor Active-Active databases running Redis database version 8.4, the `ACKED` option is not supported for trimming commands.\n\n#### Rolling upgrade limitation for clusters with custom or deprecated modules\n\nDue to module handling changes introduced in Redis Software version 8.0, upgrading a cluster that contains custom or deprecated modules, such as RedisGraph and RedisGears v2, can become stuck when adding a new node to the cluster during a rolling upgrade.\n\n#### Module commands limitation during Active-Active database upgrades to Redis 8.0\n\nWhen upgrading an Active-Active database to Redis version 8.0, you cannot use module commands until all Active-Active database instances have been upgraded. Currently, these commands are not blocked automatically.\n\n#### Redis 8.0 database cannot be created with flash\n\nYou cannot create a Redis 8.0 database with flash storage enabled. Create a Redis 8.0 database with RAM-only storage instead, or use Redis 8.2 for flash-enabled (Redis Flex) databases.\n\n#### Cluster Manager UI limitations\n\nThe following legacy UI features are not yet available in the new Cluster Manager UI:\n\n- Purge an Active-Active instance.\n\n Use [`crdb-cli crdb purge-instance`]() instead.\n\n- Search and export the log."
},
{
"id": "security",
"title": "Security",
"role": "security",
"text": "#### Redis Open Source security fixes compatibility\n\nAs part of Redis's commitment to security, Redis Software implements the latest [security fixes](https://github.com/redis/redis/releases) available with [Redis Open Source](https://github.com/redis/redis). Redis Software has already included the fixes for the relevant CVEs.\n\nSome CVEs announced for Redis Open Source do not affect Redis Software due to different or additional functionality available in Redis Software that is not available in Redis Open Source.\n\nRedis Software 8.0.10-76 supports Redis Open Source 8.4, 8.2, 8.0, 7.4, 7.2, and 6.2. Below is the list of Redis Open Source CVEs and other security vulnerabilities fixed by version.\n\nRedis 8.2.x:\n\n- RedisBloom: Restore invalid filter.\n\n- (CVE-2025-62507) A user can run the `XACKDEL` command with multiple IDs and trigger a stack buffer overflow, which can potentially lead to remote code execution.\n\n- The `HGETEX` command can lead to a buffer overflow.\n\n- Integer overflow in `hllPatLen`.\n\n- RedisBloom: Cuckoo filter counter overflow.\n\n- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes.\n\n- RedisBloom: Reachable assert in `TopK_Create`\n\n- RedisBloom: Out-of-bounds access with empty Bloom chains.\n\n- RedisBloom: Division by zero in Cuckoo filter insertion.\n\n- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user.\n\n- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service.\n\n- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution.\n\n- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution.\n\nRedis 8.0.x:\n\n- RedisBloom: Restore invalid filter.\n\n- The `HGETEX` command can lead to a buffer overflow.\n\n- Integer overflow in `hllPatLen`.\n\n- RedisBloom: Cuckoo filter counter overflow.\n\n- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes.\n\n- RedisBloom: Reachable assert in `TopK_Create`\n\n- RedisBloom: Out-of-bounds access with empty Bloom chains.\n\n- RedisBloom: Division by zero in Cuckoo filter insertion.\n\n- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user.\n\n- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service.\n\n- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution.\n\n- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution.\n\nRedis 7.4.x:\n\n- RedisBloom: Restore invalid filter.\n\n- Integer overflow in `hllPatLen`.\n\n- RedisBloom: Cuckoo filter counter overflow.\n\n- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes.\n\n- RedisBloom: Reachable assert in `TopK_Create`\n\n- RedisBloom: Out-of-bounds access with empty Bloom chains.\n\n- RedisBloom: Division by zero in Cuckoo filter insertion.\n\n- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user.\n\n- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service.\n\n- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution.\n\n- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution.\n\n- (CVE-2025-32023) An authenticated user can use a specially crafted string to trigger a stack/heap out-of-bounds write on HyperLogLog operations, which can lead to remote code execution.\n\n- (CVE-2025-21605) An unauthenticated client can cause unlimited growth of output buffers until the server runs out of memory or is terminated, which can lead to denial-of-service.\n\nRedis 7.2.x:\n\n- RedisBloom: Restore invalid filter.\n\n- Integer overflow in `hllPatLen`.\n\n- RedisBloom: Cuckoo filter counter overflow.\n\n- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes.\n\n- RedisBloom: Reachable assert in `TopK_Create`\n\n- RedisBloom: Out-of-bounds access with empty Bloom chains.\n\n- RedisBloom: Division by zero in Cuckoo filter insertion.\n\n- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user.\n\n- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service.\n\n- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution.\n\n- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution.\n\n- (CVE-2025-32023) An authenticated user can use a specially crafted string to trigger a stack/heap out-of-bounds write on HyperLogLog operations, which can lead to remote code execution.\n\n- (CVE-2025-21605) An unauthenticated client can cause unlimited growth of output buffers until the server runs out of memory or is terminated, which can lead to denial-of-service.\n\n- (CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution.\n\n- (CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as `KEYS`, `SCAN`, `PSUBSCRIBE`, `FUNCTION LIST`, `COMMAND LIST`, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes.\n\n- (CVE-2023-41056) In some cases, Redis may incorrectly handle resizing of memory buffers, which can result in incorrect accounting of buffer sizes and lead to heap overflow and potential remote code execution.\n\n- (CVE-2023-41053) Redis does not correctly identify keys accessed by `SORT_RO` and, as a result, may grant users executing this command access to keys that are not explicitly authorized by the ACL configuration. (Redis 7.2.1)\n\nRedis 7.0.x:\n\n- (CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution.\n\n- (CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as `KEYS`, `SCAN`, `PSUBSCRIBE`, `FUNCTION LIST`, `COMMAND LIST`, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes.\n\n- (CVE-2023-41056) In some cases, Redis may incorrectly handle resizing of memory buffers, which can result in incorrect accounting of buffer sizes and lead to heap overflow and potential remote code execution.\n\n- (CVE-2023-41053) Redis does not correctly identify keys accessed by `SORT_RO` and, as a result, may grant users executing this command access to keys that are not explicitly authorized by the ACL configuration. (Redis 7.0.13)\n\n- (CVE-2023-36824) Extracting key names from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading random heap memory, heap corruption, and potentially remote code execution. Specifically: using `COMMAND GETKEYS*` and validation of key names in ACL rules. (Redis 7.0.12)\n\n- (CVE-2023-28856) Authenticated users can use the `HINCRBYFLOAT` command to create an invalid hash field that will crash Redis on access. (Redis 7.0.11)\n\n- (CVE-2023-28425) Specially crafted `MSETNX` commands can lead to assertion and denial-of-service. (Redis 7.0.10)\n\n- (CVE-2023-25155) Specially crafted `SRANDMEMBER`, `ZRANDMEMBER`, and `HRANDFIELD` commands can trigger an integer overflow, resulting in a runtime assertion and termination of the Redis server process. (Redis 7.0.9)\n\n- (CVE-2023-22458) Integer overflow in the Redis `HRANDFIELD` and `ZRANDMEMBER` commands can lead to denial-of-service. (Redis 7.0.8)\n\n- (CVE-2022-36021) String matching commands (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis can cause it to hang and consume 100% CPU time. (Redis 7.0.9)\n\n- (CVE-2022-35977) Integer overflow in the Redis `SETRANGE` and `SORT`/`SORT_RO` commands can drive Redis to OOM panic. (Redis 7.0.8)\n\n- (CVE-2022-35951) Executing an `XAUTOCLAIM` command on a stream key in a specific state, with a specially crafted `COUNT` argument, may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. The problem affects Redis versions 7.0.0 or newer. (Redis 7.0.5)\n\n- (CVE-2022-31144) A specially crafted `XAUTOCLAIM` command on a stream key in a specific state may result in heap overflow and potentially remote code execution. The problem affects Redis versions 7.0.0 or newer. (Redis 7.0.4)\n\n- (CVE-2022-24834) A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson and cmsgpack libraries, and result in heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. (Redis 7.0.12)\n\n- (CVE-2022-24736) An attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result in a crash of the `redis-server` process. This issue affects all versions of Redis. (Redis 7.0.0)\n\n- (CVE-2022-24735) By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. (Redis 7.0.0)\n\nRedis 6.2.x:\n\n- RedisBloom: Restore invalid filter.\n\n- Integer overflow in `hllPatLen`.\n\n- RedisBloom: Cuckoo filter counter overflow.\n\n- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes.\n\n- RedisBloom: Reachable assert in `TopK_Create`\n\n- RedisBloom: Out-of-bounds access with empty Bloom chains.\n\n- RedisBloom: Division by zero in Cuckoo filter insertion.\n\n- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user.\n\n- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service.\n\n- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution.\n\n- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution.\n\n- (CVE-2025-32023) An authenticated user can use a specially crafted string to trigger a stack/heap out-of-bounds write on HyperLogLog operations, which can lead to remote code execution.\n\n- (CVE-2025-21605) An unauthenticated client can cause unlimited growth of output buffers until the server runs out of memory or is terminated, which can lead to denial-of-service.\n\n- (CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution.\n\n- (CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as `KEYS`, `SCAN`, `PSUBSCRIBE`, `FUNCTION LIST`, `COMMAND LIST`, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes.\n\n- (CVE-2023-28856) Authenticated users can use the `HINCRBYFLOAT` command to create an invalid hash field that will crash Redis on access. (Redis 6.2.12)\n\n- (CVE-2023-25155) Specially crafted `SRANDMEMBER`, `ZRANDMEMBER`, and `HRANDFIELD` commands can trigger an integer overflow, resulting in a runtime assertion and termination of the Redis server process. (Redis 6.2.11)\n\n- (CVE-2023-22458) Integer overflow in the Redis `HRANDFIELD` and `ZRANDMEMBER` commands can lead to denial-of-service. (Redis 6.2.9)\n\n- (CVE-2022-36021) String matching commands (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis can cause it to hang and consume 100% CPU time. (Redis 6.2.11)\n\n- (CVE-2022-35977) Integer overflow in the Redis `SETRANGE` and `SORT`/`SORT_RO` commands can drive Redis to OOM panic. (Redis 6.2.9)\n\n- (CVE-2022-24834) A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson and cmsgpack libraries, and result in heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. (Redis 6.2.13)\n\n- (CVE-2022-24736) An attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result in a crash of the `redis-server` process. This issue affects all versions of Redis. (Redis 6.2.7)\n\n- (CVE-2022-24735) By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. (Redis 6.2.7)\n\n- (CVE-2021-41099) Integer to heap buffer overflow handling certain string commands and network payloads, when `proto-max-bulk-len` is manually configured to a non-default, very large value. (Redis 6.2.6)\n\n- (CVE-2021-32762) Integer to heap buffer overflow issue in `redis-cli` and `redis-sentinel` parsing large multi-bulk replies on some older and less common platforms. (Redis 6.2.6)\n\n- (CVE-2021-32761) An integer overflow bug in Redis version 2.2 or newer can be exploited using the `BITFIELD` command to corrupt the heap and potentially result with remote code execution. (Redis 6.2.5)\n\n- (CVE-2021-32687) Integer to heap buffer overflow with intsets, when `set-max-intset-entries` is manually configured to a non-default, very large value. (Redis 6.2.6)\n\n- (CVE-2021-32675) Denial Of Service when processing RESP request payloads with a large number of elements on many connections. (Redis 6.2.6)\n\n- (CVE-2021-32672) Random heap reading issue with Lua Debugger. (Redis 6.2.6)\n\n- (CVE-2021-32628) Integer to heap buffer overflow handling ziplist-encoded data types, when configuring a large, non-default value for `hash-max-ziplist-entries`, `hash-max-ziplist-value`, `zset-max-ziplist-entries` or `zset-max-ziplist-value`. (Redis 6.2.6)\n\n- (CVE-2021-32627) Integer to heap buffer overflow issue with streams, when configuring a non-default, large value for `proto-max-bulk-len` and `client-query-buffer-limit`. (Redis 6.2.6)\n\n- (CVE-2021-32626) Specially crafted Lua scripts may result with Heap buffer overflow. (Redis 6.2.6)\n\n- (CVE-2021-32625) An integer overflow bug in Redis version 6.0 or newer can be exploited using the STRALGO LCS command to corrupt the heap and potentially result with remote code execution. This is a result of an incomplete fix by CVE-2021-29477. (Redis 6.2.4)\n\n- (CVE-2021-29478) An integer overflow bug in Redis 6.2 could be exploited to corrupt the heap and potentially result with remote code execution. The vulnerability involves changing the default set-max-intset-entries configuration value, creating a large set key that consists of integer values and using the COPY command to duplicate it. The integer overflow bug exists in all versions of Redis starting with 2.6, where it could result with a corrupted RDB or DUMP payload, but not exploited through COPY (which did not exist before 6.2). (Redis 6.2.3)\n\n- (CVE-2021-29477) An integer overflow bug in Redis version 6.0 or newer could be exploited using the STRALGO LCS command to corrupt the heap and potentially result in remote code execution. The integer overflow bug exists in all versions of Redis starting with 6.0. (Redis 6.2.3)"
}
],
"examples": []
}