Valkey 9.0 · Version Status
Valkey 9.0 End of Life Date
Valkey 9.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Valkey 9.0 is actively supported. EOL date: October 21, 2028.
EOL Date
Oct 21, 2028
896 days remaining
Latest Release
9.0.4
Standard release
Release Date
Oct 21, 2025
Valkey 9.0 series
| Version | Latest | EOL Date | Status |
|---|
| 7.2 |
7.2.13 |
Apr 16, 2029 |
Active |
| 8.0 |
8.0.9 |
Sep 15, 2027 |
Active |
| 8.1 |
8.1.7 |
Mar 31, 2030 |
Active |
| → 9.0 |
9.0.4 |
Oct 21, 2028 |
Active |
What does Valkey 9.0 end of life mean?
When Valkey 9.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Valkey 9.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Valkey 9.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Valkey 9.0 reach end of life?
Valkey 9.0 reached end of life on October 21, 2028. That is 896 days remaining.
Is Valkey 9.0 still supported?
Yes, Valkey 9.0 is currently supported. The EOL date is October 21, 2028.
What should I upgrade to from Valkey 9.0?
The recommended upgrade from Valkey 9.0 is
Valkey 9.0 — the latest actively supported version. Check the
Valkey full timeline for all supported versions.
What are the security risks of running Valkey 9.0 past EOL?
When Valkey 9.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Valkey should migrate immediately or implement compensating controls.