Redis
Redis
See the latest tracked release, confirm when it was published, and subscribe for update emails.
8.8.2
- Release date
- August 17, 2026
- Security status
- 2 high-severity CVEs tracked in the last 90 days. Current version not affected.
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 |
|---|---|---|
| 8.8.2 | 2026-08-17 | Release Notes |
| 8.8.1 | 2026-07-23 | Release Notes |
| 8.8.0 | 2026-05-25 | 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 versionnot affected | 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
|