{
  "schema_version": 2,
  "id": "operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-125",
  "title": "Redis Software release notes 8.2.0-125 (October 2026)",
  "url": "https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-125/",
  "summary": "Bug fixes for upgrades from Redis Software 7.2.x and 7.4.x, cluster management after a primary node change, node removal during upgrades, Active-Active proxy recovery, DMC proxy stability, scaling and resharding, ACL validation, cluster recovery, Google Cloud Storage backup configuration, and signing in with passwords that contain a colon. Internal fixes and improvements.",
  "tags": [
    "docs",
    "operate",
    "rs"
  ],
  "last_updated": "2026-10-20T11:01:25-05:00",
  "page_type": "content",
  "content_hash": "fcf680dacc8efa9e51c46e0df9343033e37453cc5279744a98ade6ea4bfddfff",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "This is a maintenance release for ​[​Redis Software version 8.2.0](https://redis.io/downloads/#Redis_Software)."
    },
    {
      "id": "highlights",
      "title": "Highlights",
      "role": "content",
      "text": "This version offers:\n\n- Bug fix for upgrades from Redis Software 7.2.x and 7.4.x\n\n- Bug fixes for cluster management after a primary node change\n\n- Bug fix for node removal during rolling upgrades\n\n- Bug fixes for DMC proxy stability and Active-Active proxy recovery\n\n- Bug fixes for scaling, resharding, and cluster recovery\n\n- Bug fix for ACL rule validation\n\n- Bug fix for Google Cloud Storage backup configuration\n\n- Bug fix for signing in with passwords that contain a colon\n\n- Internal fixes and improvements"
    },
    {
      "id": "new-in-this-release",
      "title": "New in this release",
      "role": "content",
      "text": ""
    },
    {
      "id": "redis-database-versions-and-feature-sets",
      "title": "Redis database versions and feature sets",
      "role": "content",
      "text": "Redis Software version 8.2.0 includes the following Redis database versions: 8.6.2, 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](https://redis.io/docs/latest/operate/rs/databases/configure/db-defaults#database-version) is 8.6.\n\nRedis Software includes multiple feature sets, compatible with different Redis database versions.\n\n\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.6 | RediSearch 8.6<br />RedisJSON 8.6<br />RedisTimeSeries 8.6<br />RedisBloom 8.6<br />See [What's new in Redis 8.6](https://redis.io/docs/latest/develop/whats-new/8-6) and [Redis Open Source 8.6 release notes](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.6-release-notes) |\n| 8.4 | RediSearch 8.4<br />RedisJSON 8.4<br />RedisTimeSeries 8.4<br />RedisBloom 8.4<br />See [What's new in Redis 8.4](https://redis.io/docs/latest/develop/whats-new/8-4) and [Redis Open Source 8.4 release notes](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.4-release-notes) |\n| 8.2 | RediSearch 8.2<br />RedisJSON 8.2<br />RedisTimeSeries 8.2<br />RedisBloom 8.2<br />See [What's new in Redis 8.2](https://redis.io/docs/latest/develop/whats-new/8-2) and [Redis Open Source 8.2 release notes](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.2-release-notes) |\n| 8.0 | RediSearch 8.0<br />RedisJSON 8.0<br />RedisTimeSeries 8.0<br />RedisBloom 8.0<br />See [What's new in Redis 8.0](https://redis.io/docs/latest/develop/whats-new/8-0) and [Redis Open Source 8.0 release notes](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisce/redisos-8.0-release-notes) |\n| 7.4 | [RediSearch 2.10](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.10-release-notes)<br />[RedisJSON 2.8](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.8-release-notes)<br />[RedisTimeSeries 1.12](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.12-release-notes)<br />[RedisBloom 2.8](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.8-release-notes) |\n| 7.2 | [RediSearch 2.8](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.8-release-notes)<br />[RedisJSON 2.6](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes)<br />[RedisTimeSeries 1.10](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.10-release-notes)<br />[RedisBloom 2.6](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.6-release-notes) |\n| 6.2 | [RediSearch 2.6](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.6-release-notes)<br />[RedisJSON 2.4](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.4-release-notes)<br />[RedisTimeSeries 1.8](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes)<br />[RedisBloom 2.4](https://redis.io/docs/latest/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.4-release-notes) |"
    },
    {
      "id": "resolved-issues",
      "title": "Resolved issues",
      "role": "content",
      "text": "- RS196137: Fixed an issue where the Cluster Manager did not send the required `private_key` field when configuring Google Cloud Storage (GCS) backups.\n\n- RS201541: Fixed an issue where removing a node could get stuck in a decommissioning state during a rolling upgrade of a cluster with AOF persistence on RHEL and Amazon Linux.\n\n- RS202231: Fixed an issue where the DMC proxy could crash while resharding a database during a scale-out.\n\n- RS202483: Fixed an issue where ACL rule validation did not apply the cluster's `acl_pubsub_default` setting, which caused validation to reject valid ACL rules or accept invalid rules that then left the database change pending.\n\n- RS209436: Fixed an issue where a proxy that started during a database failover did not resume forwarding traffic and closed client connections while the database appeared active.\n\n- RS210971: Fixed an issue where endpoint request metrics did not count requests to Memcached databases.\n\n- RS211091: Fixed an issue where the cluster could become unresponsive after a newly joined node became the primary node while scaling the cluster.\n\n- RS212081: Fixed an issue where changing the primary node could time out and leave the cluster without a working primary node.\n\n- RS212205: Fixed an issue where users with a password that contains a colon (`:`) could not sign in to the Cluster Manager UI or authenticate REST API requests.\n\n- RS212633: Fixed an issue where recovering a cluster after a full cluster restart could use outdated persistence files, which prevented the database from being recovered.\n\n- RS213016: Fixed an issue where a node that was frozen and then resumed could stop responding to cluster management requests, which caused cluster health checks to fail and left the database in an `active-change-pending` state.\n\n- RS213801: Fixed an issue where a shard could remain in the wrong role after resharding or scaling.\n\n- RS215390: Fixed an issue where a database with the `all-nodes` proxy policy could stay in an `active-change-pending` state after a node was added to the cluster.\n\n- RS215608: Fixed an issue where running `dmc-cli list bdb` or `dmc-cli list server` could corrupt memory and cause the DMC proxy to crash.\n\n- RS215676: Fixed an issue where adding a participating cluster to an Active-Active database could cause the new participating cluster's shards to crash repeatedly during the full sync, which also disrupted synchronization between the other participating clusters.\n\n- RS216045: Fixed an issue where the DMC proxy could crash repeatedly when a client sent a command without key arguments, such as `PUBSUB SHARDNUMSUB` with no channels, in a pipeline with another command.\n\n- RS219531: Fixed an issue where upgrading a cluster from Redis Software version 7.2.x or 7.4.x to version 8.2.0 could fail because a node that still ran the earlier version lost its replication link to the cluster configuration store."
    },
    {
      "id": "version-changes",
      "title": "Version changes",
      "role": "compatibility",
      "text": ""
    },
    {
      "id": "jwt-token-invalidation-on-upgrade",
      "title": "JWT token invalidation on upgrade",
      "role": "content",
      "text": "To improve system security, the JWT signing secret has changed in version 8.0.22 and later. As a result, upgrading invalidates all previously issued JWT tokens, which must be regenerated. Tokens used programmatically within the cluster are regenerated automatically. Cluster Manager users must sign out and sign in again, or wait for their session or token to expire."
    },
    {
      "id": "reserved-ports",
      "title": "Reserved ports",
      "role": "content",
      "text": "Make sure the following ports are open before upgrading Redis Software.\n\nThe following port was added as a reserved port in Redis Software version 8.0.18; however, it is optional instead of reserved in Redis Software version 8.0.20-44:\n\n| Port | Process name | Usage |\n|------|--------------|-------|\n| 3357 | reconciliation_tree_grpc | Internal communication |\n\nPorts reserved as of Redis Software version 7.22.0:\n\n| Port | Process name | Usage |\n|------|--------------|-------|\n| 3346 | cluster_api_internal | Cluster API internal port |\n| 3351 | cluster_watchdog_grpc_api | Cluster watchdog now supports gRPC |\n| 3352 | grpc_service_mesh | gRPC communication between nodes |\n| 3353 | local_grpc_service_mesh | Local gRPC services |\n| 3354 | grpc_gossip_envoy | gRPC gossip protocol communication between nodes |\n| 3355 | authentication_service | Authentication service internal port |\n\nPorts reserved as of Redis Software version 7.8.2:\n\n| Port | Process name | Usage |\n|------|--------------|-------|\n| 3347 | cert_exporter | Reports cluster certificate metrics |\n| 3348 | process_exporter | Reports process metrics for DMC and Redis processes |\n| 3349 | cluster_wd_exporter | Reports cluster watchdog metrics |\n| 3350 | db_controller | Internode communication |\n| 9091 | node_exporter | Reports host node metrics related to CPU, memory, disk, and more |\n| 9125 | statsd_exporter | Reports push metrics related to the DMC and syncer, and some cluster and node metrics |\n\nSee [Ports and port ranges used by Redis Software](https://redis.io/docs/latest/operate/rs/networking/port-configurations#ports-and-port-ranges-used-by-redis-software) for a complete list."
    },
    {
      "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](https://redis.io/docs/latest/operate/rs/references/supported-platforms) for more details about operating system compatibility.\n\n**Amazon Linux 2 is no longer supported.** Starting with Redis Software version 8.0.22, Redis Software no longer builds or publishes Amazon Linux 2 (`amzn2`) packages. Use Amazon Linux 2023 instead.\n\n\n\n<span title=\"Check mark icon\">&#x2705;</span> Supported – The platform is supported for this version of Redis Software and Redis Stack modules.\n\n<span title=\"Warning icon\" class=\"font-serif\">:warning:</span> 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<br />major versions | 8.2 | 8.0 | 7.22 | 7.8 | 7.4 | 7.2 | 6.4 | 6.2 |\n|---------------------------------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|\n| **Release date** | Jul 2026 | Oct 2025 | May 2025 | Nov 2024 | Feb 2024 | Aug 2023 | Feb 2023 | Aug 2021 |\n| [**End-of-life date**](https://redis.io/docs/latest/operate/rs/installing-upgrading/product-lifecycle#endoflife-schedule) | Determined after<br />next major release | Jul 2028 | Oct 2027 | May 2027 | Nov 2026 | Feb 2026 | Aug 2025 | Feb 2025 |\n| **Platforms** | | | | | | | | |\n| RHEL 9 &<br />compatible distros<sup>[1](#table-note-1)</sup> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | – | – | – |\n| RHEL 9<br />FIPS mode<sup>[5](#table-note-5)</sup> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | – | – | – | – |\n| RHEL 8 &<br />compatible distros<sup>[1](#table-note-1)</sup> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> |\n| RHEL 7 &<br />compatible distros<sup>[1](#table-note-1)</sup> | – | – | – | – | – | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> |\n| Ubuntu 22.04<sup>[2](#table-note-2)</sup> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | – | – | – | – |\n| Ubuntu 20.04<sup>[2](#table-note-2)</sup> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | – |\n| Ubuntu 18.04<sup>[2](#table-note-2)</sup> | – | – | – | – | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> |\n| Ubuntu 16.04<sup>[2](#table-note-2)</sup> | – | – | – | – | – | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> |\n| Amazon Linux 2023<sup>[6](#table-note-6)</sup> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | – | – | – | – | – | – |\n| Amazon Linux 2 | – | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | – |\n| Amazon Linux 1 | – | – | – | – | – | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> | <span title=\"Deprecated\" class=\"font-serif\">:warning:</span> |\n| Kubernetes<sup>[3](#table-note-3)</sup> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> |\n| Docker<sup>[4](#table-note-4)</sup> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> | <span title=\"Supported\">&#x2705;</span> |\n\n1. <a name=\"table-note-1\"></a>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. <a name=\"table-note-2\"></a>The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments.\n\n3. <a name=\"table-note-3\"></a>See the [Redis Enterprise for Kubernetes documentation](https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions) for details about support per version and Kubernetes distribution.\n\n4. <a name=\"table-note-4\"></a>[Docker images](https://redis.io/docs/latest/operate/rs/installing-upgrading/quickstarts/docker-quickstart) of Redis Software are certified for development and testing only.\n\n5. <a name=\"table-note-5\"></a>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.\n\n6. <a name=\"table-note-6\"></a>Amazon Linux 2023 support was added in Redis Software version 8.0.20."
    },
    {
      "id": "downloads",
      "title": "Downloads",
      "role": "content",
      "text": "The following table shows the SHA256 checksums for the available packages:\n\n| Package | SHA256 checksum (8.2.0-125 October release) |\n|---------|---------------------------------------|\n| Ubuntu 20 | <span class=\"break-all\">edeb44f10ac5db8648c3a1ecd4266ec4a7e73035ea2e6415468ee6596c22da00</span> |\n| Ubuntu 22 (amd64) | <span class=\"break-all\">841feb35520a76b3ee51d7635f8fd2ed511b45c43a72d212c57af10394241527</span> |\n| Ubuntu 22 (arm64) | <span class=\"break-all\">9c527e55411fafca18353db49613381c669a1189e784e87010d92b8d2556bf17</span> |\n| Red Hat Enterprise Linux (RHEL) 8 | <span class=\"break-all\">c23106b4801c07e18adc660317b6b93aa7161f5ffb4b15f74893db91c761ffe6</span> |\n| Red Hat Enterprise Linux (RHEL) 9 (amd64) | <span class=\"break-all\">8bbd7fd39ac073a7b52e1545800d66c3995719b4766a58f762b5bc66c59ab5f0</span> |\n| Red Hat Enterprise Linux (RHEL) 9 (arm64) | <span class=\"break-all\">d908c2f20579e4e6c8e1d41c91cfb5bc48403306f4741d46f81b5afa784dcb6e</span> |\n| Red Hat Enterprise Linux (RHEL) 9 FIPS (amd64) | <span class=\"break-all\">896bb24fd57bfd3aaa269ebb9a31e42337c57f3afb2cae9ee45339e21b5ecfb2</span> |\n| Amazon Linux 2023 (amd64) | <span class=\"break-all\">06ac73b6788a38f1144288db2bccab9656deaad9523de1e0b508eb26c1129e21</span> |\n| Amazon Linux 2023 (arm64) | <span class=\"break-all\">b801de92c1c1633bacd2c2ac06ffbc8586de24fe689486b8c2a04a0084e6a362</span> |"
    },
    {
      "id": "known-issues",
      "title": "Known issues",
      "role": "content",
      "text": "- RS155734: Endpoint availability metrics do not work as expected due to a calculation error.\n\n- For databases that use RedisTimeSeries with Redis database version 8.2, 8.4, or 8.6, after a shard restarts and recovers from its append-only file (AOF), requests routed to that shard can receive replies that belong to other commands or no reply at all. The issue does not resolve on its own."
    },
    {
      "id": "known-limitations",
      "title": "Known limitations",
      "role": "content",
      "text": "#### Increased memory usage in FIPS mode\n\nFIPS-enabled builds use more memory than non-FIPS builds. Each Go-based control-plane service uses roughly 34 MB more when running in FIPS mode, which adds up to approximately 210 MB of additional memory per node. Account for this overhead when sizing FIPS-enabled deployments. This limitation affects FIPS-enabled builds only.\n\n#### SFTP storage not supported in FIPS mode\n\nFIPS-enabled builds do not support SFTP as a storage location for backups, imports, or exports, because the SFTP library is not FIPS-compliant. In FIPS mode, use a different storage location. This limitation affects FIPS-enabled builds only.\n\n#### Redis Search query failures during rolling upgrades across the 8.4 version boundary\n\nRedis Search queries can fail during a rolling upgrade when a cluster contains shards running Redis versions earlier than 8.4 and shards running Redis version 8.4 or later, due to an internal protocol change introduced in version 8.4. This issue affects only clusters where `parallel_shards_upgrade` has been changed from its default value of `0`. If both conditions apply, expect Redis Search downtime until all nodes are upgraded.\n\n#### 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#### Cluster Manager sign-outs and false \"down\" status during an Active-Active upgrade\n\nWhile an Active-Active database has participating clusters running different Redis Software versions, the Cluster Manager UI on an upgraded cluster can sign users out intermittently and show a participating cluster as down, even though replication is active and the syncers are connected.\n\nThis affects the Cluster Manager UI only. It's caused by a JWT signing-key mismatch between nodes running different versions during the upgrade window (see [JWT token invalidation on upgrade](#jwt-token-invalidation-on-upgrade)). The data path and replication are not affected.\n\nTo resolve it, upgrade the remaining participating clusters. The issue clears after every participating cluster runs the same version. If you're signed out, sign in again.\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`](https://redis.io/docs/latest/operate/rs/references/cli-utilities/crdb-cli/crdb/purge-instance) instead."
    },
    {
      "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.2.0-125 supports Redis Open Source 8.6, 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\n\n\n- Memory corruption in `SLOT_INFO` handling may allow an unauthenticated user to potentially run their own code.\n\n- A use-after-free in TLS pending-data processing may allow an authenticated user to cause a denial-of-service.\n\n- A vulnerability in the `RESTORE` command and in RDB loading allows an authenticated user to trigger a use-after-free in stream consumer groups via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- An ACL key-pattern bypass in `GEORADIUS` and `GEORADIUSBYMEMBER` may allow an authenticated user to write to keys outside their permitted key patterns.\n\n- An out-of-bounds read during command key extraction may cause the server to crash.\n\n- VSET: Missing `level` cap when loading a serialized HNSW graph may lead to resource exhaustion.\n\n- VSET: Missing validation of the parameter count when loading a serialized vector set may lead to oversized allocation and resource exhaustion.\n\n- Certificate common-name handling can allow an authentication bypass when `tls-auth-clients-user` is set to `CN`.\n\n- (CVE-2026-62356) An authenticated user may trigger a heap out-of-bounds write in RedisBloom by loading a specially crafted Count-Min Sketch (`CMSketch`) object, for example via the `RESTORE` command or a crafted RDB file.\n\n- RedisBloom: Out-of-bounds access in the `TopK` heap cleanup path.\n\n- VSET: Large `VADD REDUCE` values can lead to out-of-memory crashes or buffer overflow.\n\n- (CVE-2026-23479) When a blocked client is evicted while re-executing a blocked command, an authenticated user may trigger a use-after-free and potentially lead to remote code execution.\n\n- (CVE‑2026‑25243) A vulnerability in the Redis `RESTORE` command allows an authenticated user to trigger an invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-25588) A vulnerability in the `RESTORE` command, when used with the RedisTimeSeries module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE‑2026‑25589) A vulnerability in the `RESTORE` command, when used with the RedisBloom module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-23631) An authenticated user may exploit the synchronization mechanism of the master-replica and trigger a use-after-free vulnerability, potentially leading to remote code execution. The bug affects only replicas that are configured, or may be configured with `replica-read-only` disabled, and exists in all versions of Redis with Lua scripting.\n\n- Insufficient sanitization of Lua script error messages can allow an authenticated user with `EVAL` permission to inject arbitrary RESP protocol responses, leading to denial of service, data manipulation, and connection pool poisoning.\n\n- RedisBloom: Integer overflow in `TopK` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `td_histogram_t` RDB loading may lead to heap buffer overflow.\n\n- RedisBloom: Missing validation in `CuckooFilter` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `SBChain` and `CMSketch` RDB loading may lead to heap out-of-bounds write.\n\n- Added validation of limits during RDB load and data creation to avoid resource exhaustion and Denial-of-Service (DoS) vulnerabilities.\n\n\n\n\n\n- Memory corruption in `SLOT_INFO` handling may allow an unauthenticated user to potentially run their own code.\n\n- A use-after-free in TLS pending-data processing may allow an authenticated user to cause a denial-of-service.\n\n- A vulnerability in the `RESTORE` command and in RDB loading allows an authenticated user to trigger a use-after-free in stream consumer groups via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- An ACL key-pattern bypass in `GEORADIUS` and `GEORADIUSBYMEMBER` may allow an authenticated user to write to keys outside their permitted key patterns.\n\n- An out-of-bounds read during command key extraction may cause the server to crash.\n\n- VSET: Missing `level` cap when loading a serialized HNSW graph may lead to resource exhaustion.\n\n- VSET: Missing validation of the parameter count when loading a serialized vector set may lead to oversized allocation and resource exhaustion.\n\n- (CVE-2026-62356) An authenticated user may trigger a heap out-of-bounds write in RedisBloom by loading a specially crafted Count-Min Sketch (`CMSketch`) object, for example via the `RESTORE` command or a crafted RDB file.\n\n- RedisBloom: Out-of-bounds access in the `TopK` heap cleanup path.\n\n- VSET: Large `VADD REDUCE` values can lead to out-of-memory crashes or buffer overflow.\n\n- (CVE-2026-23479) When a blocked client is evicted while re-executing a blocked command, an authenticated user may trigger a use-after-free and potentially lead to remote code execution.\n\n- (CVE‑2026‑25243) A vulnerability in the Redis `RESTORE` command allows an authenticated user to trigger an invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-25588) A vulnerability in the `RESTORE` command, when used with the RedisTimeSeries module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE‑2026‑25589) A vulnerability in the `RESTORE` command, when used with the RedisBloom module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-23631) An authenticated user may exploit the synchronization mechanism of the master-replica and trigger a use-after-free vulnerability, potentially leading to remote code execution. The bug affects only replicas that are configured, or may be configured with `replica-read-only` disabled, and exists in all versions of Redis with Lua scripting.\n\n- Insufficient sanitization of Lua script error messages can allow an authenticated user with `EVAL` permission to inject arbitrary RESP protocol responses, leading to denial of service, data manipulation, and connection pool poisoning.\n\n- RedisBloom: Integer overflow in `TopK` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `td_histogram_t` RDB loading may lead to heap buffer overflow.\n\n- RedisBloom: Missing validation in `CuckooFilter` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `SBChain` and `CMSketch` RDB loading may lead to heap out-of-bounds write.\n\n- Added validation of limits during RDB load and data creation to avoid resource exhaustion and Denial-of-Service (DoS) vulnerabilities.\n\n\n\n\n\n- Memory corruption in `SLOT_INFO` handling may allow an unauthenticated user to potentially run their own code.\n\n- A use-after-free in TLS pending-data processing may allow an authenticated user to cause a denial-of-service.\n\n- A vulnerability in the `RESTORE` command and in RDB loading allows an authenticated user to trigger a use-after-free in stream consumer groups via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- An ACL key-pattern bypass in `GEORADIUS` and `GEORADIUSBYMEMBER` may allow an authenticated user to write to keys outside their permitted key patterns.\n\n- An out-of-bounds read during command key extraction may cause the server to crash.\n\n- VSET: Missing `level` cap when loading a serialized HNSW graph may lead to resource exhaustion.\n\n- VSET: Missing validation of the parameter count when loading a serialized vector set may lead to oversized allocation and resource exhaustion.\n\n- (CVE-2026-62356) An authenticated user may trigger a heap out-of-bounds write in RedisBloom by loading a specially crafted Count-Min Sketch (`CMSketch`) object, for example via the `RESTORE` command or a crafted RDB file.\n\n- RedisBloom: Out-of-bounds access in the `TopK` heap cleanup path.\n\n- VSET: Large `VADD REDUCE` values can lead to out-of-memory crashes or buffer overflow.\n\n- (CVE-2026-23479) When a blocked client is evicted while re-executing a blocked command, an authenticated user may trigger a use-after-free and potentially lead to remote code execution.\n\n- (CVE‑2026‑25243) A vulnerability in the Redis `RESTORE` command allows an authenticated user to trigger an invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-25588) A vulnerability in the `RESTORE` command, when used with the RedisTimeSeries module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE‑2026‑25589) A vulnerability in the `RESTORE` command, when used with the RedisBloom module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-23631) An authenticated user may exploit the synchronization mechanism of the master-replica and trigger a use-after-free vulnerability, potentially leading to remote code execution. The bug affects only replicas that are configured, or may be configured with `replica-read-only` disabled, and exists in all versions of Redis with Lua scripting.\n\n- Insufficient sanitization of Lua script error messages can allow an authenticated user with `EVAL` permission to inject arbitrary RESP protocol responses, leading to denial of service, data manipulation, and connection pool poisoning.\n\n- RedisBloom: Integer overflow in `TopK` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `td_histogram_t` RDB loading may lead to heap buffer overflow.\n\n- RedisBloom: Missing validation in `CuckooFilter` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `SBChain` and `CMSketch` RDB loading may lead to heap out-of-bounds write.\n\n- Added validation of limits during RDB load and data creation to avoid resource exhaustion and Denial-of-Service (DoS) vulnerabilities.\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\n\n\n\n\n- Memory corruption in `SLOT_INFO` handling may allow an unauthenticated user to potentially run their own code.\n\n- A use-after-free in TLS pending-data processing may allow an authenticated user to cause a denial-of-service.\n\n- A vulnerability in the `RESTORE` command and in RDB loading allows an authenticated user to trigger a use-after-free in stream consumer groups via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- An ACL key-pattern bypass in `GEORADIUS` and `GEORADIUSBYMEMBER` may allow an authenticated user to write to keys outside their permitted key patterns.\n\n- An out-of-bounds read during command key extraction may cause the server to crash.\n\n- (CVE-2026-62356) An authenticated user may trigger a heap out-of-bounds write in RedisBloom by loading a specially crafted Count-Min Sketch (`CMSketch`) object, for example via the `RESTORE` command or a crafted RDB file.\n\n- RedisBloom: Out-of-bounds access in the `TopK` heap cleanup path.\n\n- VSET: Large `VADD REDUCE` values can lead to out-of-memory crashes or buffer overflow.\n\n- (CVE-2026-23479) When a blocked client is evicted while re-executing a blocked command, an authenticated user may trigger a use-after-free and potentially lead to remote code execution.\n\n- (CVE‑2026‑25243) A vulnerability in the Redis `RESTORE` command allows an authenticated user to trigger an invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-25588) A vulnerability in the `RESTORE` command, when used with the RedisTimeSeries module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE‑2026‑25589) A vulnerability in the `RESTORE` command, when used with the RedisBloom module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-23631) An authenticated user may exploit the synchronization mechanism of the master-replica and trigger a use-after-free vulnerability, potentially leading to remote code execution. The bug affects only replicas that are configured, or may be configured with `replica-read-only` disabled, and exists in all versions of Redis with Lua scripting.\n\n- Insufficient sanitization of Lua script error messages can allow an authenticated user with `EVAL` permission to inject arbitrary RESP protocol responses, leading to denial of service, data manipulation, and connection pool poisoning.\n\n- RedisBloom: Integer overflow in `TopK` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `td_histogram_t` RDB loading may lead to heap buffer overflow.\n\n- RedisBloom: Missing validation in `CuckooFilter` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `SBChain` and `CMSketch` RDB loading may lead to heap out-of-bounds write.\n\n- Added validation of limits during RDB load and data creation to avoid resource exhaustion and Denial-of-Service (DoS) vulnerabilities.\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\n\n\n\n\n- Memory corruption in `SLOT_INFO` handling may allow an unauthenticated user to potentially run their own code.\n\n- A use-after-free in TLS pending-data processing may allow an authenticated user to cause a denial-of-service.\n\n- A vulnerability in the `RESTORE` command and in RDB loading allows an authenticated user to trigger a use-after-free in stream consumer groups via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- An ACL key-pattern bypass in `GEORADIUS` and `GEORADIUSBYMEMBER` may allow an authenticated user to write to keys outside their permitted key patterns.\n\n- An out-of-bounds read during command key extraction may cause the server to crash.\n\n- (CVE-2026-62356) An authenticated user may trigger a heap out-of-bounds write in RedisBloom by loading a specially crafted Count-Min Sketch (`CMSketch`) object, for example via the `RESTORE` command or a crafted RDB file.\n\n- RedisBloom: Out-of-bounds access in the `TopK` heap cleanup path.\n\n- (CVE-2026-23479) When a blocked client is evicted while re-executing a blocked command, an authenticated user may trigger a use-after-free and potentially lead to remote code execution.\n\n- (CVE‑2026‑25243) A vulnerability in the Redis `RESTORE` command allows an authenticated user to trigger an invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-25588) A vulnerability in the `RESTORE` command, when used with the RedisTimeSeries module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE‑2026‑25589) A vulnerability in the `RESTORE` command, when used with the RedisBloom module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-23631) An authenticated user may exploit the synchronization mechanism of the master-replica and trigger a use-after-free vulnerability, potentially leading to remote code execution. The bug affects only replicas that are configured, or may be configured with `replica-read-only` disabled, and exists in all versions of Redis with Lua scripting.\n\n- Insufficient sanitization of Lua script error messages can allow an authenticated user with `EVAL` permission to inject arbitrary RESP protocol responses, leading to denial of service, data manipulation, and connection pool poisoning.\n\n- RedisBloom: Integer overflow in `TopK` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `td_histogram_t` RDB loading may lead to heap buffer overflow.\n\n- RedisBloom: Missing validation in `CuckooFilter` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `SBChain` and `CMSketch` RDB loading may lead to heap out-of-bounds write.\n\n- Added validation of limits during RDB load and data creation to avoid resource exhaustion and Denial-of-Service (DoS) vulnerabilities.\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\n\n\n\n- Memory corruption in `SLOT_INFO` handling may allow an unauthenticated user to potentially run their own code.\n\n- A use-after-free in TLS pending-data processing may allow an authenticated user to cause a denial-of-service.\n\n- A vulnerability in the `RESTORE` command and in RDB loading allows an authenticated user to trigger a use-after-free in stream consumer groups via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- An ACL key-pattern bypass in `GEORADIUS` and `GEORADIUSBYMEMBER` may allow an authenticated user to write to keys outside their permitted key patterns.\n\n- An out-of-bounds read during command key extraction may cause the server to crash.\n\n- (CVE-2026-62356) An authenticated user may trigger a heap out-of-bounds write in RedisBloom by loading a specially crafted Count-Min Sketch (`CMSketch`) object, for example via the `RESTORE` command or a crafted RDB file.\n\n- RedisBloom: Out-of-bounds access in the `TopK` heap cleanup path.\n\n- (CVE-2026-23479) When a blocked client is evicted while re-executing a blocked command, an authenticated user may trigger a use-after-free and potentially lead to remote code execution.\n\n- (CVE‑2026‑25243) A vulnerability in the Redis `RESTORE` command allows an authenticated user to trigger an invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-25588) A vulnerability in the `RESTORE` command, when used with the RedisTimeSeries module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE‑2026‑25589) A vulnerability in the `RESTORE` command, when used with the RedisBloom module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-23631) An authenticated user may exploit the synchronization mechanism of the master-replica and trigger a use-after-free vulnerability, potentially leading to remote code execution. The bug affects only replicas that are configured, or may be configured with `replica-read-only` disabled, and exists in all versions of Redis with Lua scripting.\n\n- Insufficient sanitization of Lua script error messages can allow an authenticated user with `EVAL` permission to inject arbitrary RESP protocol responses, leading to denial of service, data manipulation, and connection pool poisoning.\n\n- RedisBloom: Integer overflow in `TopK` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `td_histogram_t` RDB loading may lead to heap buffer overflow.\n\n- RedisBloom: Missing validation in `CuckooFilter` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `SBChain` and `CMSketch` RDB loading may lead to heap out-of-bounds write.\n\n- Added validation of limits during RDB load and data creation to avoid resource exhaustion and Denial-of-Service (DoS) vulnerabilities.\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\n\n\n\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\n\n\n\n\n- Memory corruption in `SLOT_INFO` handling may allow an unauthenticated user to potentially run their own code.\n\n- A use-after-free in TLS pending-data processing may allow an authenticated user to cause a denial-of-service.\n\n- A vulnerability in the `RESTORE` command and in RDB loading allows an authenticated user to trigger a use-after-free in stream consumer groups via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- An ACL key-pattern bypass in `GEORADIUS` and `GEORADIUSBYMEMBER` may allow an authenticated user to write to keys outside their permitted key patterns.\n\n- An out-of-bounds read during command key extraction may cause the server to crash.\n\n- (CVE-2026-62356) An authenticated user may trigger a heap out-of-bounds write in RedisBloom by loading a specially crafted Count-Min Sketch (`CMSketch`) object, for example via the `RESTORE` command or a crafted RDB file.\n\n- RedisBloom: Out-of-bounds access in the `TopK` heap cleanup path.\n\n- (CVE-2026-23479) When a blocked client is evicted while re-executing a blocked command, an authenticated user may trigger a use-after-free and potentially lead to remote code execution.\n\n- (CVE‑2026‑25243) A vulnerability in the Redis `RESTORE` command allows an authenticated user to trigger an invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-25588) A vulnerability in the `RESTORE` command, when used with the RedisTimeSeries module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE‑2026‑25589) A vulnerability in the `RESTORE` command, when used with the RedisBloom module, allows an authenticated attacker to trigger invalid memory access via a specially crafted serialized payload, potentially resulting in remote code execution.\n\n- (CVE-2026-23631) An authenticated user may exploit the synchronization mechanism of the master-replica and trigger a use-after-free vulnerability, potentially leading to remote code execution. The bug affects only replicas that are configured, or may be configured with `replica-read-only` disabled, and exists in all versions of Redis with Lua scripting.\n\n- Insufficient sanitization of Lua script error messages can allow an authenticated user with `EVAL` permission to inject arbitrary RESP protocol responses, leading to denial of service, data manipulation, and connection pool poisoning.\n\n- RedisBloom: Integer overflow in `TopK` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `td_histogram_t` RDB loading may lead to heap buffer overflow.\n\n- RedisBloom: Missing validation in `CuckooFilter` RDB loading may lead to heap out-of-bounds access.\n\n- RedisBloom: Missing validation in `SBChain` and `CMSketch` RDB loading may lead to heap out-of-bounds write.\n\n- Added validation of limits during RDB load and data creation to avoid resource exhaustion and Denial-of-Service (DoS) vulnerabilities.\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": []
}