Database-scoped management roles. Data path command auditing.

Redis Software version 8.2 is now available!

Highlights

This version offers:

• Database-scoped management roles
• Data path command auditing
• FIPS 140-3 support

Detailed release notes

For more detailed release notes, select a build version from the following table:

Version (Release date) | Major changes | Redis Open Source compatibility
8.2.0-46 (August 2026) | Bug fixes for internal certificate rotation, rolling upgrades, the Cluster Manager UI, shard rebalancing, and Active-Active synchronization. Internal fixes and improvements. | Redis 8.6.2, 8.4.0, 8.2.1, 8.0.2, 7.4.3, 7.2.7, 6.2.13
8.2.0-25 (July 2026) | Database-scoped management roles. Data path command auditing. | Redis 8.6.2, 8.4.0, 8.2.1, 8.0.2, 7.4.3, 7.2.7, 6.2.13

Version changes

Breaking changes

Redis Software version 8.2.0 introduces the following breaking changes:

• Local import from Redis Software system directories is no longer supported. To improve security, database imports that use the mount_point source can no longer read files from Redis Software system directories, including /opt/redislabs, /var/opt/redislabs, /etc/opt/redislabs, and any of their subdirectories.
  • Import operations that reference files in these directories now fail.
  • Store import files in a non-system location accessible to Redis Software before you start the import.
• smtp_password is now a write-only field in the Cluster API. To improve security, the API no longer returns the SMTP password in responses to GET /v1/cluster, and the Cluster Manager UI no longer reads or displays the existing password.
  • Applications or scripts that previously expected smtp_password to be returned by the Cluster API no longer receive this field.
  • When you update SMTP settings, the existing password cannot be retrieved. To change the SMTP password, provide a new password as part of the update request.
• Custom module upload is disabled by default. To improve security, custom (user-defined) module uploads are now disabled by default. A new cluster setting, allow_modules_upload, controls access to the custom module upload APIs. When this setting is disabled (the default), requests to POST /v2/modules/user-defined and POST /v2/local/modules/user-defined/artifacts return 403 modules_upload_disabled, regardless of user role.
  • To enable custom module uploads, set allow_modules_upload to true with a PUT /v1/cluster request.
  • Applications or automation that call the custom module upload APIs directly receive a 403 modules_upload_disabled response until the setting is enabled.
  • Existing functionality for listing, deleting, and loading modules is unchanged.

Reserved ports

Make sure the following ports are open before upgrading Redis Software.

The 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:

Port | Process name | Usage
3357 | reconciliation_tree_grpc | Internal communication

Ports reserved as of Redis Software version 7.22.0:

Port | Process name | Usage
3346 | cluster_api_internal | Cluster API internal port
3351 | cluster_watchdog_grpc_api | Cluster watchdog now supports gRPC
3352 | grpc_service_mesh | gRPC communication between nodes
3353 | local_grpc_service_mesh | Local gRPC services
3354 | grpc_gossip_envoy | gRPC gossip protocol communication between nodes
3355 | authentication_service | Authentication service internal port

Ports reserved as of Redis Software version 7.8.2:

Port | Process name | Usage
3347 | cert_exporter | Reports cluster certificate metrics
3348 | process_exporter | Reports process metrics for DMC and Redis processes
3349 | cluster_wd_exporter | Reports cluster watchdog metrics
3350 | db_controller | Internode communication
9091 | node_exporter | Reports host node metrics related to CPU, memory, disk, and more
9125 | statsd_exporter | Reports push metrics related to the DMC and syncer, and some cluster and node metrics

See Ports and port ranges used by Redis Software for a complete list.

Deprecations

API deprecations

• The db_conns_auditing cluster policy and database configuration field is deprecated. Use the audit_settings.audit_mode field instead. Setting db_conns_auditing to true is equivalent to setting audit_mode to connection. See Audit events for the current auditing configuration.
• The gradual_src_mode, gradual_sync_mode, and gradual_sync_max_shards_per_source parameters are deprecated. Use gradual_sync_policy instead. You can set it with rladmin tune db or the REST API.
• The old_password field in POST /v1/users/password and PUT /v1/users/password requests is deprecated and ignored. It was optional and had no effect when adding or resetting a password, so you can remove it from these requests. old_password is still required for DELETE /v1/users/password, which uses it to identify the password to delete.
• The following REST API fields, deprecated since Redis Software version 6.4.2, are removed in this release:
  • use_ipv6 (cluster object) — use use_external_ipv6 instead.
  • redis_cleanup_job_settings (job scheduler object) — use persistence_cleanup_scan_interval instead.

Internal monitoring and v1 Prometheus metrics deprecation

The existing internal monitoring engine is deprecated. We recommend transitioning to the new metrics stream engine for improved performance, enhanced integration capabilities, and modernized metrics streaming.

V1 Prometheus metrics are deprecated but still available. To transition to the new metrics stream engine, either migrate your existing dashboards using this guide or use new preconfigured dashboards.

As part of the transition to the metrics stream engine, some internal cluster manager alerts were deprecated in favor of external monitoring solutions. See the alerts transition plan for guidance.

Supported platforms

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.

✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules.
⚠️ Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release.

(Platform support table omitted for brevity)

Known issues

• RS155734: Endpoint availability metrics do not work as expected due to a calculation error.

Known limitations

Redis Search query failures during rolling upgrades across the 8.4 version boundary

Redis 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.

Trim ACKED not supported for Active-Active 8.4 databases

For Active-Active databases running Redis database version 8.4, the ACKED option is not supported for trimming commands.

Rolling upgrade limitation for clusters with custom or deprecated modules

Due 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.

Module commands limitation during Active-Active database upgrades to Redis 8.0

When 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.

Redis 8.0 database cannot be created with flash

You 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.

New Cluster Manager UI limitations

The following legacy UI features are not yet available in the new Cluster Manager UI:

• Purge an Active-Active instance. Use crdb-cli crdb purge-instance instead.
• Search and export the log.

SCAN results can be inconsistent during a rolling upgrade in OSS Cluster API mode

During a rolling upgrade with Smart client handoffs (SCH) enabled, when some slot's shards have migrated to a different node but are still reachable from their original node, results of the SCAN command might be inconsistent: it might show some of the keys, it might show keys that are not reachable from that node, or it might show no keys. When the slot migration is done, this issue will fix itself.

Original source

Warning

Redis Software 7.2 reached end of life on February 28, 2026. It no longer receives security patches, bug fixes, or maintenance releases. Support for 7.2-specific issues is limited per your subscription agreement, and you may be asked to upgrade before an issue can be investigated.

Upgrade to a supported version. See the supported upgrade paths and the Redis Software product lifecycle.

Redis Enterprise Software version 7.2.4 is now available!

Highlights

This version offers:

• Redis 7.0 and 7.2 features
• Auto Tiering (enhanced successor to Redis on Flash)
• RESP3 support
• Sharded pub/sub
• A preview of the new Cluster Manager UI (admin console)
• Redis Stack 7.2 features
• Three Redis database versions: 7.2, 6.2, 6.0
• License file structure updates
• Redis ACL selectors and enhanced key-based permissions
• New INFO fields
• Log rotation enhancements
• Multi-OS upgrade support for clusters with modules

Detailed release notes

For more detailed release notes, select a build version from the following table:

7.2.4-154 (July 2026): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-153 (April 2026): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-138 (September 2025): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-132 (June 2025): Bug fix for mismatched key counts in Active-Active databases after cluster recovery. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-130 (May 2025): Retry mechanism for listener creation on database ports. Bug fix for Lua out-of-memory errors preventing scripts from running Redis commands. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-122 (March 2025): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-109 (May 2024): Bug fixes. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-105 (February 2024): LDAP authentication timeout is configurable using the REST API. RHEL 8.9 support. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-92 (November 2023): New Cluster Manager UI enhancements - LDAP configuration improvements. New capability_name field added to module REST API object. Automatic removal of deprecated, predefined roles and ACLs upon cluster upgrade, unless they are associated with any users or databases. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-72 (October 2023): New Cluster Manager UI enhancements - database upgrade configuration, database defaults, user lockout parameters, and TLS configuration improvements. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-64 (September 2023): Improved cluster recovery with manually uploaded modules. Support package contains supervisorctl status. Configure port range using rladmin and REST API. License API returns the number of used shards (RAM & flash). OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-52 (August 2023): Redis 7.0 and 7.2 features. Auto Tiering (enhanced successor to Redis on Flash). RESP3 support. Sharded pub/sub. Preview of the new Cluster Manager UI. Redis Stack 7.2 features. Three Redis database versions. License file structure updates. Redis ACL selectors and enhanced key-based permissions. New INFO fields. Log rotation enhancements. Multi-OS upgrade support for clusters with modules. OSS Redis compatibility: Redis 7.2.0, 6.2.13, 6.0.20

[Additional sections on version changes, breaking changes, deprecations, command deprecations, API deprecations, access control deprecations, legacy UI, RedisGraph end-of-life, platform support, known issues, known limitations, command limitations, module loading issues, cluster recovery, and other technical details follow in the full release notes.]

Original source

Bug fixes

Bug fixes for internal certificate rotation, rolling upgrades, the Cluster Manager UI, shard rebalancing, and Active-Active synchronization. Internal fixes and improvements.

Database-scoped management roles. Data path command auditing.

FIPS 140-3 support

Redis Software version 8.2.0 introduces the following breaking changes

• Local import from Redis Software system directories is no longer supported. To improve security, database imports that use the mount_point source can no longer read files from Redis Software system directories, including /opt/redislabs, /var/opt/redislabs, /etc/opt/redislabs, and any of their subdirectories.
  • Import operations that reference files in these directories now fail.
  • Store import files in a non-system location accessible to Redis Software before you start the import.
• smtp_password is now a write-only field in the Cluster API. To improve security, the API no longer returns the SMTP password in responses to GET /v1/cluster, and the Cluster Manager UI no longer reads or displays the existing password.
  • Applications or scripts that previously expected smtp_password to be returned by the Cluster API no longer receive this field.
  • When you update SMTP settings, the existing password cannot be retrieved. To change the SMTP password, provide a new password as part of the update request.
• Custom module upload is disabled by default. To improve security, custom (user-defined) module uploads are now disabled by default. A new cluster setting, allow_modules_upload, controls access to the custom module upload APIs. When this setting is disabled (the default), requests to POST /v2/modules/user-defined and POST /v2/local/modules/user-defined/artifacts return 403 modules_upload_disabled, regardless of user role.
  • To enable custom module uploads, set allow_modules_upload to true with a PUT /v1/cluster request.
  • Applications or automation that call the custom module upload APIs directly receive a 403 modules_upload_disabled response until the setting is enabled.
  • Existing functionality for listing, deleting, and loading modules is unchanged.

Original source

Highlights

This version offers:

• Redis 7.0 and 7.2 features
• Auto Tiering (enhanced successor to Redis on Flash)
• RESP3 support
• Sharded pub/sub
• A preview of the new Cluster Manager UI (admin console)
• Redis Stack 7.2 features
• Three Redis database versions: 7.2, 6.2, 6.0
• License file structure updates
• Redis ACL selectors and enhanced key-based permissions
• New INFO fields
• Log rotation enhancements
• Multi-OS upgrade support for clusters with modules

Detailed release notes

For more detailed release notes, select a build version from the following table:

7.2.4-154 (July 2026): Internal fixes and improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-153 (April 2026): Internal fixes and improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-138 (September 2025): Internal fixes and improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-132 (June 2025): Bug fix for mismatched key counts in Active-Active databases after cluster recovery. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-130 (May 2025): Retry mechanism for listener creation on database ports. Bug fix for Lua out-of-memory errors preventing scripts from running Redis commands. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-122 (March 2025): Internal fixes and improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-109 (May 2024): Bug fixes. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-105 (February 2024): LDAP authentication timeout is configurable using the REST API. RHEL 8.9 support. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-92 (November 2023): New Cluster Manager UI enhancements - LDAP configuration improvements. New capability_name field added to module REST API object. Automatic removal of deprecated, predefined roles and ACLs upon cluster upgrade, unless they are associated with any users or databases. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-72 (October 2023): New Cluster Manager UI enhancements - database upgrade configuration, database defaults, user lockout parameters, and TLS configuration improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-64 (September 2023): Improved cluster recovery with manually uploaded modules. Support package contains supervisorctl status. Configure port range using rladmin and REST API. License API returns the number of used shards (RAM & flash). Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-52 (August 2023): Redis 7.0 and 7.2 features. Auto Tiering (enhanced successor to Redis on Flash). RESP3 support. Sharded pub/sub. Preview of the new Cluster Manager UI. Redis Stack 7.2 features. Three Redis database versions. License file structure updates. Redis ACL selectors and enhanced key-based permissions. New INFO fields. Log rotation enhancements. Multi-OS upgrade support for clusters with modules. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

[Additional sections on version changes, breaking changes, deprecations, command deprecations, API deprecations, access control deprecations, legacy UI, RedisGraph end-of-life, platform support, known issues, known limitations, command limitations, module loading issues, cluster recovery, and other technical details are included in the full release notes.]

Original source

Redis Software 8! The most performant, most secure, and richest version so far. Built for performance, scale, and reliability to power modern ML and AI applications.

Redis Software version 8.0 is now available!

Highlights

This version offers:

• Redis 8.0, 8.2, 8.4, and 8.6 feature set versions
• Performance improvements and memory reduction
• New vector set data structure
• Redis Flex revamped engine
• Redis Search upgrades
• Lag-aware availability API
• Metrics stream engine (General Availability)
• Simplified module management
• New REST API fields for database and cluster configuration
• Customer-managed certificates for internode encryption
• Smart client handoffs

Detailed release notes

For more detailed release notes, select a build version from the following table:

8.0.20-44 (June 2026): Enabled client_eviction by default to fix an issue where a massive volume of traffic directed at a single hot key could cause high latency and out-of-memory errors. Bug fixes for Active-Active databases, LDAP, and ACLs. Internal fixes and improvements.

Compatible with Redis 8.6.2, 8.4.0, 8.2.1, 8.0.2, 7.4.3, 7.2.7, 6.2.13.

Version changes

• POST /v1/cluster/actions/change_master REST API requests will no longer allow a node that exists but is not finished bootstrapping to become the primary node. Such requests will now return the status code 406 Not Acceptable.
• Node status now returns the actual provisional RAM and flash values even when the maximum number of shards on the node (max_redis_servers) is reached. Previously, the API returned 0 for provisional_ram_of_node and provisional_flash_of_node when a node reached its shard limit. This change affects REST API node status requests and the rladmin status nodes command's output.
• crdb_controller is enabled by default as of Redis Software version 8.0.18.

Breaking changes

• Upgrading to Redis Software versions 8.0.10 through 8.0.16-29 can cause LDAP authentication to fail with "certificate signed by unknown authority" errors if your cluster currently uses LDAP authentication. Fixed in Redis Software version 8.0.16-33.
• For versions 8.0.2 through 8.0.10, LDAP filters for user_dn_query and dn_group_query strictly require parentheses. Fixed in version 8.0.16.
• Redis Software installation script changes: changed --skip-updating-env-path option to --update-env-path when running install.sh. Changed skip_updating_env_path parameter to update_env_path in the installation answers file.

Redis database version 8 breaking changes

When new major versions of Redis Open Source change existing commands, upgrading your database to a new version can potentially break functionality. Read the breaking changes to update your applications accordingly.

ACL behavior changes

Redis 8 includes all Query Engine, JSON, time series, Bloom filter, cuckoo filter, top-k, count-min sketch, and t-digest commands in existing ACL categories such as @read, @write, etc., affecting command access permissions.

Redis Search changes

Validation and behavioral updates to Redis Search commands including LIMIT argument validation, parsing rules for FT.CURSOR READ and FT.ALIASADD, parentheses requirement for APPLY expressions, error handling improvements, scoring updates, and better handling of expired records and malformed fields.

OpenSSL version

Redis Software version 8.0.16 and later requires OpenSSL 3.3 or later.

Reserved ports

List of reserved ports as of this and prior versions; see the full Ports and port ranges used by Redis Software documentation.

Deprecations

API deprecations include policy field for bootstrap requests, module_args field for database requests, and event_archive_cleanup_task_settings for job_scheduler requests.

Redis Search deprecations

Deprecated commands, options, vector search options, configuration parameters, and dialects detailed.

Internal monitoring and v1 Prometheus metrics deprecation

The existing internal monitoring engine is deprecated. Transition to new metrics stream engine recommended. V1 metrics still available with migration guides.

Supported platforms

Table of supported platforms and versions with notes on deprecations and compatibility.

Known issues

Lists specific issues such as LDAP filter failures, Active Directory LDAP authentication UI issue with workaround, SSO IPv6 limitations with workaround, ACL migration issues, endpoint availability metrics miscalculation.

Known limitations

Includes Redis Search query failures during rolling upgrades across 8.4 version boundary if parallel_shards_upgrade is changed from 0; Trim ACKED not supported for Active-Active 8.4 databases; rolling upgrade limitations for clusters with custom or deprecated modules like RedisGraph and RedisGears v2; module command usage restrictions during Active-Active database upgrades to Redis 8.0; Redis 8.0 databases cannot be created with flash storage enabled.

New Cluster Manager UI limitations

Legacy UI features not yet available include purging an Active-Active instance (use crdb-cli crdb purge-instance instead) and search/export of the log.

Original source

Redis Software 8

The most performant, most secure, and richest version so far. Built for performance, scale, and reliability to power modern ML and AI applications.

Redis Software version 8.0 is now available!

Highlights

This version offers:

• Redis 8.0, 8.2, 8.4, and 8.6 feature set versions
• Performance improvements and memory reduction
• New vector set data structure
• Redis Flex revamped engine
• Redis Search upgrades
• Lag-aware availability API
• Metrics stream engine (General Availability)
• Simplified module management
• New REST API fields for database and cluster configuration
• Customer-managed certificates for internode encryption
• Smart client handoffs

Detailed release notes

For more detailed release notes, select a build version from the following table:

8.0.20-44 (June 2026)

Enabled client_eviction by default to fix an issue where a massive volume of traffic directed at a single hot key could cause high latency and out-of-memory errors. Bug fixes for Active-Active databases, LDAP, and ACLs. Internal fixes and improvements.

Redis 8.6.2, 8.4.0, 8.2.1, 8.0.2, 7.4.3, 7.2.7, 6.2.13

Version changes

• POST /v1/cluster/actions/change_master REST API requests will no longer allow a node that exists but is not finished bootstrapping to become the primary node. Such requests will now return the status code 406 Not Acceptable.
• Node status now returns the actual provisional RAM and flash values even when the maximum number of shards on the node (max_redis_servers) is reached. Previously, the API returned 0 for provisional_ram_of_node and provisional_flash_of_node when a node reached its shard limit. This change affects REST API node status requests and the rladmin status nodes command's output.
• crdb_controller is enabled by default as of Redis Software version 8.0.18.

Breaking changes

• Upgrading to Redis Software version 8.0.10 through 8.0.16-29 can cause LDAP authentication to fail with "certificate signed by unknown authority" errors if your cluster currently uses LDAP authentication. This issue was fixed in Redis Software version 8.0.16-33.
• For Redis Software versions 8.0.2 through 8.0.10, LDAP filters for user_dn_query and dn_group_query strictly require parentheses to function correctly. Filters that previously worked without parentheses will no longer work after upgrading to these versions. For example, you must include the parentheses in (sAMAccountName=%u). As of version 8.0.16, this breaking change no longer applies, and both (sAMAccountName=%u) and sAMAccountName=%u are valid filters.
• Redis Software installation script changes:
  • Changed the --skip-updating-env-path option to --update-env-path when running install.sh.
  • Changed the skip_updating_env_path parameter to update_env_path in the installation answers file.

Redis database version 8 breaking changes

When new major versions of Redis Open Source change existing commands, upgrading your database to a new version can potentially break some functionality. Before you upgrade, read the provided list of breaking changes that affect Redis Software and update any applications that connect to your database to handle these changes.

ACL behavior changes

Before Redis 8, the existing ACL categories @read, @write, @dangerous, @admin, @slow, and @fast did not include commands for Redis Search and the JSON, time series, and probabilistic data structures.
Starting with Redis 8, Redis includes all Query Engine, JSON, time series, Bloom filter, cuckoo filter, top-k, count-min sketch, and t-digest commands in these existing ACL categories.

As a result:

• Existing ACL rules such as +@read +@write will allow access to more commands than in previous versions of Redis. Examples:
  • A user with +@read access will be able to execute FT.SEARCH.
  • A user with +@write access will be able to execute JSON.SET.
• ACL rules such as +@all -@write will allow access to fewer commands than previous versions of Redis.
  • For example, a user with +@all -@write will not be able to execute JSON.SET.
• Explicit inclusion of new command categories is required to maintain access. The new categories are: @search, @json, @timeseries, @bloom, @cuckoo, @topk, @cms, and @tdigest.
• ACL rules such as +@read +JSON.GET can now be simplified as +@read because JSON.GET is included in the @read category.

Note that the @all category did not change, as it always included all the commands.

Redis Search changes

The following changes affect behavior and validation in Redis Search:

• Enforces validation for LIMIT arguments (offset must be 0 if limit is 0).
• Enforces parsing rules for FT.CURSOR READ and FT.ALIASADD.
• Parentheses are now required for exponentiation precedence in APPLY expressions.
• Invalid input now returns errors instead of empty results.
• Default values revisited for reducers like AVG, COUNT, SUM, STDDEV, QUANTILE, and others.
• Updates to scoring (BM25 is now the default instead of TF-IDF).
• Improved handling of expired records, memory constraints, and malformed fields.

OpenSSL version

Redis Software version 8.0.16 and later requires OpenSSL 3.3 or later.

Reserved ports

Make sure the following ports are open before upgrading Redis Software.

The 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:

• Port 3357 - reconciliation_tree_grpc - Internal communication

Deprecations

API deprecations

• Deprecated the policy field for bootstrap REST API requests. Use PUT /v1/cluster/policy to change cluster policies after cluster creation instead.
• Deprecated the module_args field for database REST API requests. Use the new module configuration objects search, timeseries, and probabilistic instead.
• Deprecated event_archive_cleanup_task_settings for job_scheduler REST API requests.

Redis Search deprecations

• Deprecated commands: FT.ADD, FT.SAFEADD, FT.DEL, FT.GET, FT.MGET, FT.SYNADD, FT.DROP, FT._DROPIFX, and FT.CONFIG.
• Deprecated FT.SEARCH options: GEOFILTER, FILTER, and NOSTOPWORDS.
• Deprecated vector search options: INITIAL_CAP and BLOCK_SIZE.
• Deprecated configuration parameters: WORKER_THREADS, MT_MODE, PRIVILEGED_THREADS_NUM, and GCSCANSIZE.
• Deprecated dialects: DIALECT 1, DIALECT 3, and DIALECT 4.

Internal monitoring and v1 Prometheus metrics deprecation

The existing internal monitoring engine is deprecated. We recommend transitioning to the new metrics stream engine for improved performance, enhanced integration capabilities, and modernized metrics streaming.
V1 Prometheus metrics are deprecated but still available. To transition to the new metrics stream engine, either migrate your existing dashboards using this guide or use new preconfigured dashboards.
As part of the transition to the metrics stream engine, some internal cluster manager alerts were deprecated in favor of external monitoring solutions. See the alerts transition plan for guidance.

Supported platforms

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.

✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules.

⚠️ Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release.

Known issues

• RS196225: After upgrading to Redis Software version 8.0.x, previously working LDAP filters that use an OR clause to match multiple attributes can fail to find a unique DN for some users. This issue was fixed in Redis Software version 8.0.20-44.
• RS193156: Active Directory LDAP authentication can fail in the Cluster Manager UI after upgrading to Redis Software version 8.0.16-33 due to an issue with LDAP TLS client certificate handling. Users previously authenticated through Active Directory can no longer sign in to the Cluster Manager UI after the upgrade. As a workaround, configure an LDAP client certificate using an update cluster certificates REST API request. See Create certificates and Update certificates for more detailed instructions. This issue was fixed in Redis Software version 8.0.18.
• RS180550: You cannot set up SSO when the Cluster Manager UI is exposed through an IPv6-based load balancer or gateway. As a workaround, use an IPv4-based address for the SSO service base address, or register a DNS name that resolves to the IPv6 address. This issue was fixed in Redis Software version 8.0.10.
• RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors. This issue was fixed in Redis Software version 8.0.6.
• RS155734: Endpoint availability metrics do not work as expected due to a calculation error.

Known limitations

Redis Search query failures during rolling upgrades across the 8.4 version boundary

Redis 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.

Trim ACKED not supported for Active-Active 8.4 databases

For Active-Active databases running Redis database version 8.4, the ACKED option is not supported for trimming commands.

Rolling upgrade limitation for clusters with custom or deprecated modules

Due 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.

Module commands limitation during Active-Active database upgrades to Redis 8.0

When 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.

Redis 8.0 database cannot be created with flash

You 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.

New Cluster Manager UI limitations

The following legacy UI features are not yet available in the new Cluster Manager UI:

• Purge an Active-Active instance. Use crdb-cli crdb purge-instance instead.
• Search and export the log.

Original source

Redis Enterprise Software release notes 7.4.x

New Cluster Manager UI enhancements, including Active-Active database management. Full TLS 1.3 support. Automatic recovery configuration. Full IPv6 support, including for internal traffic. Maintenance mode enhancements. Module management enhancements. RHEL 9 support.

Redis Enterprise Software version 7.4 is now available!

Highlights

This version offers:

• New Cluster Manager UI enhancements, including Active-Active database management
• Full TLS 1.3 support
• Automatic recovery configuration
• Full IPv6 support, including for internal traffic
• Maintenance mode enhancements
• Module management enhancements
• RHEL 7 and Oracle Linux 7, which were previously deprecated, are no longer supported
• RHEL 9 support

Detailed release notes

For more detailed release notes, select a build version from the following table:

7.4.6-280 (June 2026): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.6-279 (February 2026): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.6-272 (September 2025): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.6-268 (June 2025): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.6-232 (March 2025): Internal fixes and improvements. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.6-188 (January 2025): Bug fix for a memory leak in the DMC proxy process. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.6-102 (October 2024): Updated module feature sets with later versions of RediSearch and RedisTimeSeries. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.6-77 (September 2024): Updated module feature sets. Bug fixes. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.6-22 (July 2024): Support for SHA-384 certificates in client authentication. New parameters for optimize_shard_placement and recover database REST API requests. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.2-216 (July 2024): region_name field for new AWS S3 regions. Bug fixes. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.2-169 (May 2024): Configuration options for cluster management API workers and threads. Reduced Cluster Configuration Store CPU usage. OSS Redis compatibility: Redis 7.2.4, 6.2.13, 6.0.20
7.4.2-129 (April 2024): Fixes for bugs and known limitations that affect Redis Enterprise Software v7.4.2-126. OSS Redis compatibility: Redis 7.2.3, 6.2.13, 6.0.20
7.4.2-126 (April 2024): Redis database version selection during database creation in the Cluster Manager UI. New Redis logo. OSS Redis compatibility: Redis 7.2.3, 6.2.13, 6.0.20
7.4.2-104 (March 2024): New Cluster Manager UI enhancements to change passwords from the sign-in screen, view locked user accounts, and unlock user accounts with password reset. OSS Redis compatibility: Redis 7.2.3, 6.2.13, 6.0.20
7.4.2-54 (February 2024): New Cluster Manager UI enhancements, including Active-Active database management. Full TLS 1.3 support. Automatic recovery configuration. Full IPv6 support, including for internal traffic. Maintenance mode enhancements. Module management enhancements. RHEL 9 support. OSS Redis compatibility: Redis 7.2.3, 6.2.13, 6.0.20

Version changes

Product lifecycle updates

End-of-life policy extension

The end-of-life policy for Redis Enterprise Software versions 6.2 and later has been extended to 24 months after the formal release of the subsequent major version. For the updated end-of-life schedule, see the Redis Enterprise Software product lifecycle.

Supported upgrade paths

Redis Enterprise Software versions 6.2.4 and 6.2.8 do not support direct upgrades beyond version 7.4.x. Versions 6.2.10, 6.2.12, and 6.2.18 are part of the upgrade path. To upgrade from 6.2.4 or 6.2.8 to versions later than 7.4.x, an intermediate upgrade is required.
The next major Redis Enterprise Software release will still bundle Redis database version 6.2 and allow database upgrades from Redis database version 6.2 to 7.x.
See the Redis Enterprise Software product lifecycle for more information about release numbers.

Deprecations

API deprecations

• The replica HA cluster policy is deprecated.
• The maintenance mode option keep_slave_shards is deprecated in rladmin and the REST API. Use evict_ha_replica and evict_active_active_replica instead.
• /v1/debuginfo REST API paths are deprecated. Use the new paths /v1/cluster/debuginfo, /v1/nodes/debuginfo, and /v1/bdbs/debuginfo instead.

Legacy UI deprecation

The legacy UI is deprecated in favor of the new Cluster Manager UI and will be removed in a future release.

Redis 6.0 database deprecation

Redis database version 6.0 is deprecated as of Redis Enterprise Software version 7.4.2 and will be removed in a future release.
To prepare for the future removal of Redis 6.0:

1. For Redis Enterprise 6.2.* clusters, upgrade Redis 6.0 databases to Redis 6.2. See the Redis 6.2 release notes for the list of changes.
2. For Redis Enterprise 7.2.4 and 7.4.x clusters, upgrade Redis 6.0 databases to Redis 7.2. Before you upgrade your databases, see the list of Redis 7.2 breaking changes and update any applications that connect to your database to handle these changes.

End of triggers and functions preview

The triggers and functions (RedisGears) preview has been discontinued.

• Commands such as TFCALL, TFCALLASYNC, and TFUNCTION will be deprecated and will return error messages.
• Any JavaScript functions stored in Redis will be removed.
• JavaScript-based triggers will be blocked.
• Lua functions and scripts will not be affected.

If your database currently uses triggers and functions, you need to:

1. Adjust your applications to accommodate these changes.
2. Delete all triggers and functions libraries from your existing database:
   a. Run TFUNCTION LIST.
   b. Copy all library names.
   c. Run TFUNCTION DELETE for each library in the list.

If any triggers and functions libraries remain in the database, the RDB snapshot won't load on a cluster without RedisGears.
3. Migrate your database to a new database without the RedisGears module.

RedisGraph end of life

Redis has announced the end of life for RedisGraph. Redis will continue to support all RedisGraph customers, including releasing patch versions until January 31, 2025.
See the RedisGraph end-of-life announcement for more details.

Operating system retirements

• RHEL 7 and Oracle Linux 7 were previously announced as deprecated in the Redis Enterprise Software 7.2.4 release notes. As of Redis Enterprise Software 7.4.2, RHEL 7 and Oracle Linux 7 are no longer supported.

Security retirements

• The RC4 encryption cipher, which was previously deprecated in favor of stronger ciphers, is no longer supported.
• The 3DES encryption cipher, which was previously deprecated in favor of stronger ciphers like AES, is no longer supported. Verify that all clients, applications, and connections support the AES cipher.
• TLS 1.0 and TLS 1.1 connections, which were previously deprecated in favor of TLS 1.2 or later, are no longer supported. Verify that all clients, applications, and connections support TLS 1.2 or later.

Upcoming changes

Default image change for Redis Enterprise Software containers

Starting with the next major version, Redis Enterprise Software containers with the image tag x.y.z-build will be based on RHEL instead of Ubuntu.
This change will only affect you if you use containers outside the official Redis Enterprise for Kubernetes product and use Ubuntu-specific commands.
To use Ubuntu-based images after this change, you can specify the operating system suffix in the image tag. For example, use the image tag 7.4.2-216.focal instead of 7.4.2-216.

Supported platforms

The following table provides a snapshot of supported platforms as of this Redis Enterprise Software release. See the supported platforms reference for more details about operating system compatibility.
✅ Supported – The platform is supported for this version of Redis Enterprise Software and Redis Stack modules.
⚠️ Deprecation warning – The platform is still supported for this version of Redis Enterprise Software, but support will be removed in a future release.

Known issues

• RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors.
• RS61676: Full chain certificate update fails if any certificate in the chain does not have a Common Name (CN).
• RS119958: The debuginfo script fails with the error /bin/tar: Argument list too long if there are too many RocksDB log files. This issue only affects clusters with Auto Tiering.
• RS122570: REST API POST /crdbs responds with a confusing error message if the cluster does not have the requested CRDB-compatible module that complies with the requested featureset. This issue was fixed in Redis Enterprise Software version 7.4.2-126.
• RS123142: In an Active-Active setup with at least three participating clusters, removing and re-adding a cluster after removing older clusters without re-adding them can cause missing keys and potentially lead to data loss or data inconsistency. To prevent this issue, avoid adding clusters until you upgrade to the upcoming maintenance release when available. This issue was fixed in Redis Enterprise Software version 7.4.2-169.

Known limitations

New Cluster Manager UI limitations

The following legacy UI features are not yet available in the new Cluster Manager UI:

• Remove a node. Use the REST API or legacy UI instead. See Remove a cluster node for instructions.
• Purge an Active-Active instance. Use crdb-cli crdb purge-instance instead.
• Search and export the log.

OpenSSL compatibility issue for 7.4.2 modules on Amazon Linux 2

Due to an OpenSSL 1.1 compatibility issue between modules and clusters, Redis Enterprise Software version 7.4.2-54 is not fully supported on Amazon Linux 2 clusters with databases that use the following modules: RedisGears, RediSearch, or RedisTimeSeries. This issue will be fixed in a future maintenance release.

RedisGraph prevents upgrade to RHEL 9

You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Enterprise cluster contains a RedisGraph module, even if unused by any database. The RedisGraph module has reached End-of-Life and is completely unavailable in RHEL 9.

Cannot create Redis v6.x Active-Active databases with modules

You cannot create Active-Active databases that use Redis version 6.0 or 6.2 with modules. Databases that use Redis version 7.2 do not have this limitation. This limitation was fixed in Redis Enterprise Software version 7.4.2-104.

Firewalld configuration fails on RHEL 9 due to file permissions

When you install Redis Enterprise Software version 7.4.2 on RHEL 9, firewalld configuration fails to add the redislabs service if /etc/firewalld/services/redislabs-clients.xml and /etc/firewalld/services/redislabs.xml are owned by redislabs instead of root.
As a workaround:

1. Change the files' owner and group to root:
   $ chown root:root /etc/firewalld/services/redislabs-clients.xml
   $ chown root:root /etc/firewalld/services/redislabs.xml
2. Add the redislabs service to firewalld:
   $ systemctl daemon-reload
   $ systemctl restart firewalls
   $ /bin/firewall-cmd --add-service=redislabs

This limitation was fixed in Redis Enterprise Software version 7.4.2-129.

Original source

Pub/sub ACLs & default permissions. Validate client certificates by subject attributes. Ubuntu 20.04 support.

Redis Enterprise Software version 6.4.2 is now available!

This version offers:

• Extended validation of client certificates via mTLS (mutual TLS) full subject support
• Support for default restrictive permissions when using publish/subscribe commands and access control lists (ACLs)
• Enhanced TLS performance when Redis returns large arrays in responses
• Compatibility with open source Redis 6.2.7 and 6.2.10.
• Additional enhancements and bug fixes

Detailed release notes

For more detailed release notes, select a build version from the following table:

6.4.2-131 (September 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-127 (June 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-121 (March 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-115 (Oct 2024): RediSearch v2.6.23. RedisBloom v2.4.12. RedisTimeSeries v1.8.15. Compatible with Redis 6.2.10, 6.0.17
6.4.2-110 (May 2024): RedisGraph v2.10.15. RedisBloom v2.4.8. Bug fixes. Compatible with Redis 6.2.10, 6.0.17
6.4.2-103 (October 2023): RHEL 8.8 support. RediSearch v2.6.12. RedisGraph v2.10.12. RedisTimeSeries v1.8.11 Log when CCS schema changes. Bug fixes. Compatible with Redis 6.2.10, 6.0.17
6.4.2-94 (July 2023): Look-ahead mechanism for planner attempts. Package OS compatibility validation. Compatible with Redis 6.2.10, 6.0.17
6.4.2-81 (June 2023): Email alerts for database backup failures and replica high availability shard relocation failures. Compatible with Redis 6.2.10, 6.0.17
6.4.2-69 (May 2023): Amazon Linux 2 support. Configure envoy ports using rladmin. Added option to avoid specific nodes when using the optimized shards placement API. Added failure_detection_sensitivity to replace watchdog_profile. Compatible with Redis 6.2.10, 6.0.17
6.4.2-61 (April 2023): Amazon Linux 2 support. Fixed known limitations for custom installation on RHEL 7 and RHEL 8, running rl_rdbconvert manually, and resharding rack-aware databases with no replication. Compatible with Redis 6.2.10, 6.0.17
6.4.2-43 (March 2023): Ubuntu 20.04 support. Safe node removal. Allow gossip_envoy port configuration. Compatible with Redis 6.2.10, 6.0.17
6.4.2-30 (February 2023): Pub/sub ACLs & default permissions. Validate client certificates by subject attributes. Compatible with Redis 6.2.7, 6.0.16

Original source

Redis Software release notes 7.8.6-263 (May 2026)

Internal fixes and improvements.

This is a maintenance release for Redis Software version 7.8.6.

Highlights

This version offers:

• Internal fixes and improvements

New in this release

Redis database versions

Redis Software version 7.8.6 includes three Redis database versions: 7.4.0, 7.2.4, and 6.2.13.
The default Redis database version is 7.4.

Redis module feature sets

Redis Software comes packaged with several modules. As of version 7.8.2, Redis Software includes three feature sets, compatible with different Redis database versions.
The following table shows which Redis modules are compatible with each Redis database version included in this release.

Redis database version | Compatible Redis modules
7.4 | RediSearch 2.10 RedisJSON 2.8 RedisTimeSeries 1.12 RedisBloom 2.8
7.2 | RediSearch 2.8 RedisJSON 2.6 RedisTimeSeries 1.10 RedisBloom 2.6
6.2 | RediSearch 2.6 RedisJSON 2.4 RedisTimeSeries 1.8 RedisBloom 2.4 RedisGraph v2.10

1. RedisGraph end-of-life has been announced and will be removed in a future release. See the RedisGraph end-of-life announcement for more details.

Version changes

Supported platforms

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.
✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules.
⚠️ Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release.

[Table of supported platforms omitted for brevity]

1. 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.
2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments.
3. See the Redis Enterprise for Kubernetes documentation for details about support per version and Kubernetes distribution.
4. Docker images of Redis Software are certified for development and testing only.
5. Supported only if FIPS was enabled during RHEL installation to ensure FIPS compliance.

Downloads

The following table shows the SHA256 checksums for the available packages:

Package | SHA256 checksum (7.8.6-263 April release)
Ubuntu 20 | 012e7289a1cac79412b6f448a0f318fa4ddcaafebaf522ca53e1ed096d30f329
Ubuntu 22 | f936c51117c4027f21bbe07408a52f9ae10c6bfc646624bb8dd474cd99b91eae
Red Hat Enterprise Linux (RHEL) 8 | c3f8749cab066f7ab80883dbbdf27547d6d9450efccb98e2bcab44c1b45b29ae
Red Hat Enterprise Linux (RHEL) 9 | 115a5a7cc217ce4703a12db482bf900ee68705019a4478337c48b2bee6a90deb
Amazon Linux 2 | d51139976ba446573725d38a33300c9aa1354546b0fb2dd72c7525cb7881d867

Known issues

• RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors.

Known limitations

Upload modules before OS upgrade

If the cluster contains any databases that use modules, you must upload module packages for the target OS version to a node in the existing cluster before you upgrade the cluster's operating system.
See Upgrade a cluster's operating system for detailed upgrade instructions.

New Cluster Manager UI limitations

The following legacy UI features are not yet available in the new Cluster Manager UI:

• Purge an Active-Active instance. Use crdb-cli crdb purge-instance instead.
• Search and export the log.

RedisGraph prevents upgrade to RHEL 9

You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Software cluster contains a RedisGraph module, even if unused by any database. The RedisGraph module has reached End-of-Life and is completely unavailable in RHEL 9.

Query results might include hash keys with lazily expired fields

If one or more fields of a hash key expire after an FT.SEARCH or FT.AGGREGATE query begins, Redis does not account for these lazily expired fields. As a result, keys with expired fields might still be included in the query results, leading to potentially incorrect or inconsistent results.

Security

Open source Redis security fixes compatibility

As part of Redis's commitment to security, Redis Software implements the latest security fixes available with open source Redis. Redis Software has already included the fixes for the relevant CVEs.
Some CVEs announced for open source Redis do not affect Redis Software due to different or additional functionality available in Redis Software that is not available in open source Redis.

Redis Software 7.8.6-263 supports open source Redis 7.4, 7.2, and 6.2. Below is the list of open source Redis CVEs and other security vulnerabilities fixed by version.

[Detailed CVE list omitted for brevity]

Original source

Pub/sub ACLs & default permissions. Validate client certificates by subject attributes. Ubuntu 20.04 support.

Warning:

Redis Software 6.4 reached end of life on August 31, 2025. It no longer receives security patches, bug fixes, or maintenance releases. Support for 6.4-specific issues is limited per your subscription agreement, and you may be asked to upgrade before an issue can be investigated.

Upgrade to a supported version. Reaching the latest version may require an intermediate upgrade first — see the

supported upgrade paths

and the

Redis Software product lifecycle

.

Redis Enterprise Software version 6.4.2

is now available!

This version offers:

• Extended validation of client certificates via mTLS (mutual TLS) full subject support
• Support for default restrictive permissions when using publish/subscribe commands and access control lists (ACLs)
• Enhanced TLS performance when Redis returns large arrays in responses
• Compatibility with

open source Redis

6.2.7 and 6.2.10.

• Additional enhancements and bug fixes

Detailed release notes

For more detailed release notes, select a build version from the following table:

6.4.2-131 (September 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-127 (June 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-121 (March 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-115 (Oct 2024): RediSearch v2.6.23. RedisBloom v2.4.12. RedisTimeSeries v1.8.15. Compatible with Redis 6.2.10, 6.0.17
6.4.2-110 (May 2024): RedisGraph v2.10.15. RedisBloom v2.4.8. Bug fixes. Compatible with Redis 6.2.10, 6.0.17
6.4.2-103 (October 2023): RHEL 8.8 support. RediSearch v2.6.12. RedisGraph v2.10.12. RedisTimeSeries v1.8.11 Log when CCS schema changes. Bug fixes. Compatible with Redis 6.2.10, 6.0.17
6.4.2-94 (July 2023): Look-ahead mechanism for planner attempts. Package OS compatibility validation. Compatible with Redis 6.2.10, 6.0.17
6.4.2-81 (June 2023): Email alerts for database backup failures and replica high availability shard relocation failures. Compatible with Redis 6.2.10, 6.0.17
6.4.2-69 (May 2023): Amazon Linux 2 support. Configure envoy ports using rladmin. Added option to avoid specific nodes when using the optimized shards placement API. Added failure_detection_sensitivity to replace watchdog_profile. Compatible with Redis 6.2.10, 6.0.17
6.4.2-61 (April 2023): Amazon Linux 2 support. Fixed known limitations for custom installation on RHEL 7 and RHEL 8, running rl_rdbconvert manually, and resharding rack-aware databases with no replication. Compatible with Redis 6.2.10, 6.0.17
6.4.2-43 (March 2023): Ubuntu 20.04 support. Safe node removal. Allow gossip_envoy port configuration. Compatible with Redis 6.2.10, 6.0.17
6.4.2-30 (February 2023): Pub/sub ACLs & default permissions. Validate client certificates by subject attributes. Compatible with Redis 6.2.7, 6.0.16

Deprecations

Ubuntu 16 support is considered deprecated and will be removed in a future release. Ubuntu 16.04 LTS (Xenial) has reached the end of its free initial five-year security maintenance period as of April 30, 2021.

Active-Active database persistence

The RDB snapshot option for

Active-Active database persistence

is deprecated and will be removed in a future release.

Please plan to reconfigure any Active-Active databases to use append-only file (AOF) persistence with the following command:

crdb-cli crdb update --crdb-guid <CRDB_GUID> \
--default-db-config '{"data_persistence": "aof", "aof_policy":"appendfsync-every-sec"}'

TLS 1.0 and TLS 1.1

TLS 1.0 and TLS 1.1 connections are considered deprecated in favor of TLS 1.2 or later. Please verify that all clients, apps, and connections support TLS 1.2. Support for the earlier protocols will be removed in a future release. Certain operating systems, such as RHEL 8, have already removed support for the earlier protocols. Redis Enterprise Software cannot support connection protocols that are not supported by the underlying operating system.

3DES encryption cipher

The 3DES encryption cipher is considered deprecated in favor of stronger ciphers like AES. Please verify that all clients, apps, and connections support the AES cipher. Support for 3DES will be removed in a future release. Certain operating systems, such as RHEL 8, have already removed support for 3DES. Redis Enterprise Software cannot support cipher suites that are not supported by the underlying operating system.

Known limitations and Feature limitations

• RS97971 - Resharding fails for rack-aware databases with no replication (fixed and resolved as part of v6.4.2-61).
• RS101204 - High memory consumption caused by the persistence_mgr service when AOF persistence is configured for every second (fixed and resolved as part of v6.4.2-81).
• RS40641 - API requests are redirected to an internal IP in case the request arrives from a node which is not the master. To avoid this issue, use rladmin cluster config to configure handle_redirects or handle_metrics_redirects.
• RS51144, RS102128 - Active-Active: To start successfully, the syncer (crdt-syncer) must connect to all sources. In multi-cluster configurations (more than 2 A-A clusters participating), in some cases, if one or more of the clusters is not available, A-A replication will be down.
• RS123142 - In an Active-Active setup with at least three participating clusters, removing and re-adding a cluster after removing older clusters without re-adding them can cause missing keys and potentially lead to data loss or data inconsistency. This issue will be fixed in a future maintenance release. To prevent this issue, avoid adding clusters until you upgrade to the upcoming maintenance release when available.

Resharding fails for rack-aware databases with no replication

When a database is configured as rack-aware and replication is turned off, the resharding operation fails.

RS97971 - This limitation was fixed and resolved as part of v6.4.2-61.

Workaround:

Before resharding your database, turn off rack awareness:

curl -k -u "<user>:<password>" -H "Content-type: application/json" -d '{"rack_aware": false}' -X PUT "https://localhost:9443/v1/bdbs/<bdb_uid>"

After the resharding process is complete, you can re-enable rack awareness:

curl -k -u "<user>:<password>" -H "Content-type: application/json" -d '{"rack_aware": true}' -X PUT "https://localhost:9443/v1/bdbs/<bdb_uid>"

Installation limitations

Several Redis Enterprise Software installation reference files are installed to the directory /etc/opt/redislabs/ even if you use custom installation directories.

As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.
2. Mount /etc/opt/redislabs to one of the custom, non-root directories.

Upgrade limitations

Before you upgrade a cluster that hosts Active-Active databases with modules to v6.4.2-30, perform the following steps:

1. Use crdb-cli to verify that the modules (modules) and their versions (in module_list) are as they appear in the database configuration and in the default database configuration:

crdb-cli crdb get --crdb-guid <crdb-guid>

1. From the admin console's redis modules tab, validate that these modules with their specific versions are loaded to the cluster.

2. If one or more of the modules/versions are missing or if you need help, contact Redis support before taking additional steps.

This limitation has been fixed and resolved as of v6.4.2-43.

Operating system limitations

RHEL 7 and RHEL 8:

RS95344 - CRDB database will not start on Redis Enterprise v6.4.2 with a custom installation path.

For a workaround, use the following commands to add the relevant CRDB files to the Redis library:

$ yum install -y chrpath
$ find $installdir -name "crdt.so" |
xargs -n1 -I {} /bin/bash -c 'chrpath -r ${libdir} {}'

This limitation has been fixed and resolved as of v6.4.2-61.

RHEL 8:

Due to module binary differences between RHEL 7 and RHEL 8, you cannot upgrade RHEL 7 clusters to RHEL 8 when they host databases using modules. Instead, you need to create a new cluster on RHEL 8 and then migrate existing data from your RHEL 7 cluster. This does not apply to clusters that do not use modules.

Ubuntu 20.04:

By default, you cannot use the SHA1 hash algorithm (OpenSSL’s default security level is set to 2). The operating system will reject SHA1 certificates even if the mtls_allow_weak_hashing option is enabled. You need to replace SHA1 certificates with newer certificates that use SHA-256. Note that the certificates provided with Redis Enterprise Software use SHA-256.

Modules not supported for Amazon Linux 2 release candidate:

A database with modules cannot reside on an Amazon Linux 2 (release candidate) node. Support was added as part of v6.4.2-69.

Original source

Internal fixes and improvements

This is a maintenance release for 026Redis Enterprise Software version 6.4.2.

Highlights

This version offers:

026Internal fixes and improvements

New in this release

Redis modules

Redis Enterprise Software version 6.4.2-131 includes the following Redis Stack modules:

026RediSearch v2.6

026RedisJSON v2.4

026RedisBloom v2.4

026RedisGraph v2.10

026RedisTimeSeries v1.8

Version changes

Supported platforms

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.

✅ Supported 026The platform is supported for this version of Redis Enterprise Software and Redis Stack modules.
⚠️ Deprecation warning 026The platform is still supported for this version of Redis Enterprise Software, but support will be removed in a future release.

Downloads

The following table shows the MD5 checksums for the available packages:

Security

Open source Redis security fixes compatibility

As part of Redis's commitment to security, Redis Enterprise Software implements the latest security fixes available with open source Redis. Redis Enterprise has already included the fixes for the relevant CVEs.

Some CVEs announced for open source Redis do not affect Redis Enterprise due to different or additional functionality available in Redis Enterprise that is not available in open source Redis.

Redis Enterprise 6.4.2-131 supports open source Redis 6.2 and 6.0. Below is the list of open source Redis CVEs and other security vulnerabilities fixed by version.

Redis 6.2.x:

026RedisBloom: Cuckoo filter counter overflow.

026RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes.

026RedisBloom: Reachable assert in TopK_Create

026RedisBloom: Out-of-bounds access with empty Bloom chains.

026RedisBloom: Division by zero in Cuckoo filter insertion.

026(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.

026(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.

026(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.

026(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.

026(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.

026(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.

026(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.

026(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.

026(CVE-2023-45145) The wrong order of listen(2) and chmod(2) calls creates a race condition that can be used by another process to bypass desired Unix socket permissions on startup. (Redis 6.2.14)

026(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)

026(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)

026(CVE-2023-22458) Integer overflow in the Redis HRANDFIELD and ZRANDMEMBER commands can lead to denial-of-service. (Redis 6.2.9)

026(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)

026(CVE-2022-35977) Integer overflow in the Redis SETRANGE and SORT / SORT_RO commands can drive Redis to OOM panic. (Redis 6.2.9)

026(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)

026(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)

026(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)

026(CVE-2021-41099) Integer to heap buffer overflow can occur when 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)

026(CVE-2021-32762) Integer to heap buffer overflow issue in redis-cli and redis-sentinel can occur when parsing large multi-bulk replies on some older and less common platforms. (Redis 6.2.6)

026(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)

026(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)

026(CVE-2021-32675) Denial Of Service when processing RESP request payloads with a large number of elements on many connections. (Redis 6.2.6)

026(CVE-2021-32672) Random heap reading issue with Lua Debugger. (Redis 6.2.6)

026(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)

026(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)

026(CVE-2021-32626) Specially crafted Lua scripts may result with Heap buffer overflow. (Redis 6.2.6)

026(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)

026(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)

026(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)

Redis 6.0.x:

026RedisBloom: Cuckoo filter counter overflow.

026RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes.

026RedisBloom: Reachable assert in TopK_Create

026RedisBloom: Out-of-bounds access with empty Bloom chains.

026RedisBloom: Division by zero in Cuckoo filter insertion.

026(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.0.20)

026(CVE-2023-28856) Authenticated users can use the HINCRBYFLOAT command to create an invalid hash field that will crash Redis on access. (Redis 6.0.19)

026(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.0.18)

026(CVE-2022-36021) String matching commands (like SCAN or KEYS) with a specially crafted pattern to trigger a denial-of-service attack on Redis, causing it to hang and consume 100% CPU time. (Redis 6.0.18)

026(CVE-2022-35977) Integer overflow in the Redis SETRANGE and SORT / SORT_RO commands can drive Redis to OOM panic. (Redis 6.0.17)

Original source