Valkey · Lifecycle Status

Valkey End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Valkey versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Valkey 9.1.1 is actively supported. Next EOL: version 8.0 on September 15, 2027.
Running an EOL version? Get matched with support options — free ↓
📅 Get reminded before Valkey 8.0 reaches EOL on September 15, 2027 — alerts 90, 30 & 7 days out.
Google →
Latest Active
9.1.1
9.1 series
Next EOL
8.0
Sep 15, 2027
Active Versions
5
of 5 total
EOL Versions
0
no longer patched
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20242025202620272028202920307.28.08.19.09.1TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
7.2 7.2.14 Aug 15, 2023 Apr 16, 2029 981 days remaining Active
8.0 8.0.10 Sep 15, 2024 Sep 15, 2027 402 days remaining Active
8.1 8.1.9 Mar 31, 2025 Mar 31, 2030 1330 days remaining Active
9.0 9.0.5 Oct 21, 2025 Oct 21, 2028 804 days remaining Active
9.1 9.1.1 May 19, 2026 TBD Supported Active
Valkey EOL status badge Live EOL badge for your README — updates automatically at every build. [![Valkey EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fvalkey.json)](https://endoflife.ai/valkey)

What does Valkey end of life mean for your organization?

When a version of Valkey reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Valkey should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Valkey reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Valkey versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get Valkey Support Options

When Valkey versions reach end of life, security patches stop — the CVEs keep coming. The good news: extended support for Valkey exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Valkey?
The next Valkey version reaching EOL is 8.0 on September 15, 2027. See the full table above for all version EOL dates.
When is the Valkey support end date?
The next Valkey support end date is September 15, 2027, when version 8.0 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Valkey?
The latest active version of Valkey is 9.1.1. Always verify against the table above as support windows can change.
What happens when Valkey reaches end of life?
When Valkey reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Valkey?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Valkey versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →
Valkey end-of-life status badge