Redis vulnerabilities: known CVEs & security history
Redis · Database · 8 tracked CVEs · 0 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Redis release lines — 8 in total. A CVE here doesn't mean your version is affected — check Redis's current status and the safe version to run.
Known Redis CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2025-49844 | critical | 9.9 | 82% | 2025 |
| CVE-2026-25243 | high | 8.8 | 3% | 2026 |
| CVE-2026-23479 | high | 8.8 | 1% | 2026 |
| CVE-2025-62507 | high | 8.8 | 7% | 2025 |
| CVE-2026-23631 | high | 8.1 | 2% | 2026 |
| CVE-2025-46817 | high | 7 | 4% | 2025 |
| CVE-2025-46819 | medium | 6.3 | 1% | 2025 |
| CVE-2025-46818 | medium | 6 | 1% | 2025 |
Is my Redis version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Redis version → · Monitor Redis for new CVEs →
Redis vulnerabilities — frequently asked
How many known vulnerabilities does Redis have?
IsItPatched tracks 8 CVEs for Redis. 1 is critical-severity and 5 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Redis have any actively-exploited vulnerabilities?
None of Redis's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Redis vulnerability?
Among tracked issues, CVE-2025-49844 (CRITICAL, CVSS 9.9) ranks highest — a Use-after-free weakness.
Is Redis safe to use?
It depends on the version. The latest supported Redis release (8.10.2) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Redis security status · Redis end-of-life · actively-exploited CVEs. Always verify against Redis's advisories — see our disclaimer.