Valkey 9.1 · Version Status

Valkey 9.1 End of Life Date

Valkey 9.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

✓ Valkey 9.1 is actively supported. EOL date: TBD.
EOL Date
TBD
Supported
Latest Release
9.1.0
Standard release
Release Date
May 19, 2026
Valkey 9.1 series
← Valkey 9.0 All Valkey versions
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 →  ·  View score card →
All Valkey Versions
VersionLatestEOL DateStatus
7.2 7.2.13 Apr 16, 2029 Active
8.0 8.0.9 Sep 15, 2027 Active
8.1 8.1.8 Mar 31, 2030 Active
9.0 9.0.4 Oct 21, 2028 Active
→ 9.1 9.1.0 EOL Active

What does Valkey 9.1 end of life mean?

When Valkey 9.1 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.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Valkey 9.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Valkey 9.1 reach end of life?
Valkey 9.1 has already reached end of life.
Is Valkey 9.1 still supported?
Yes, Valkey 9.1 is currently supported. The EOL date is TBD.
What should I upgrade to from Valkey 9.1?
The recommended upgrade from Valkey 9.1 is Valkey 9.1 — the latest actively supported version. Check the Valkey full timeline for all supported versions.
What are the security risks of running Valkey 9.1 past EOL?
When Valkey 9.1 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.
Data from endoflife.date API · Generated at build time · How we source data →