Redis
Redis
See the latest tracked release, confirm when it was published, and subscribe for update emails.
7.4.11
- Release date
- August 17, 2026
- Security status
- Current version appears affected by 5 high-severity CVEs.
Source
GitHub API
Public release notes are linked for the latest stored release.
Release history
See the latest published releases stored for this product.
| Version | Published | Notes |
|---|---|---|
| 7.4.11 | 2026-08-17 | Release Notes |
| 7.4.10 | 2026-07-23 | Release Notes |
| 7.4.9 | 2026-05-05 | Release Notes |
| 7.4.8 | 2026-02-23 | Release Notes |
Vulnerability tracking
versionPing monitors CVEs for this product. Matching CVEs are listed below. We only display CVEs with a CVSS score of 7.0 or higher that were published within the last 90 days.
Affected status is inferred from published affected version ranges where available. Always verify against the vendor advisory before making production decisions.
| CVE | Severity | Published | Status | Summary |
|---|---|---|---|---|
| CVE-2026-81934 | HIGH (7.5) | 2026-08-27 | Current versionnot affected | Redis contains a use-after-free vulnerability in the 'tlsProcessPendingData()' function, which handles the TLS pending-data list if Redis is configured with TLS support. A remote, unauthenticated attacker may be able to execute arbitrary commands with the privileges of the Redis server. Affected versions
Show 6 more
|
| CVE-2026-66373 | HIGH (7.5) | 2026-07-25 | Current versionaffected | Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243. Affected versions
|
| CVE-2026-25243 | HIGH (7.7) | 2026-05-05 | Current versionaffected | Redis is an in-memory data structure store. In versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may lead to remote code execution. A workaround is to restrict access to the RESTORE command with ACL rules. This is patched in version 8.6.3. Affected versions
|
| CVE-2026-23479 | HIGH (7.7) | 2026-05-05 | Current versionaffected | Redis is an in-memory data structure store. In redis-server from 7.2.0 until 8.6.3, the unblock client flow does not handle an error return from `processCommandAndResetClient` when re-executing a blocked command. If a blocked client is evicted during this flow, an authenticated attacker can trigger a use-after-free that may lead to remote code execution. This has been patched in version 8.6.3. Affected versions
|
| CVE-2025-49844 | CRITICAL (10.0) | 2025-10-03 | Current versionaffected | Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands. Affected versions
|
| CVE-2025-46817 | HIGH (7.0) | 2025-10-03 | Current versionaffected | Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. Affected versions
|