Valkey 9.2 · Version Status

Valkey 9.2 End of Life Date

Valkey 9.2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ Valkey 9.2 is actively supported. EOL date: November 19, 2031.
📅 Get reminded before Valkey 9.2 reaches EOL on November 19, 2031 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
Automating this check? GET https://api.endoflife.ai/v1/score/valkey/9.2 returns this version's end-of-life date, its source and the EOL Risk Score as JSON. Get a free API key (150 requests a day, no expiry).
EOL Date
Nov 19, 2031
1824 days remaining
Latest Release
9.2.0
Standard release
Release Date
Nov 19, 2026
Valkey 9.2 series
Where these dates come from
End of lifeNov 19, 2031Vendor's own page (our correction) · valkey.io · checked Nov 20, 2026medium · 1 source agrees
End of active supportNov 19, 2029Vendor's own page (our correction) · valkey.io · checked Nov 20, 2026medium · 1 source agrees
ReleaseNov 19, 2026Vendor's own page (our correction) · valkey.io · checked Nov 20, 2026medium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Valkey 9.2 was released on November 19, 2026 and support is scheduled to end on November 19, 2031 — a planned supported lifespan of 5 years, in line with the 5 years median for Valkey releases. Its most recent patch is 9.2.0, published November 19, 2026.

← Valkey 9.1 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.16 Apr 16, 2029 Active
8.0 8.0.13 Sep 15, 2027 Active
8.1 8.1.12 Mar 31, 2030 Active
9.0 9.0.8 Oct 21, 2028 Active
9.1 9.1.4 May 19, 2031 Active
→ 9.2 9.2.0 Nov 19, 2031 Active

What does Valkey 9.2 end of life mean?

When Valkey 9.2 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Valkey 9.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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

Frequently Asked Questions
When does Valkey 9.2 reach end of life?
Valkey 9.2 reaches end of life on November 19, 2031. That is 1824 days remaining.
Is Valkey 9.2 still supported?
Yes, Valkey 9.2 is currently supported. The EOL date is November 19, 2031.
What should I upgrade to from Valkey 9.2?
The recommended upgrade from Valkey 9.2 is Valkey 9.2 — the latest actively supported version. Check the Valkey full timeline for all supported versions.
What are the security risks of running Valkey 9.2 past EOL?
When Valkey 9.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Valkey should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →