Red Hat Data Grid End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Red Hat Data Grid versions. Dates read at the vendor's own lifecycle pages (access.redhat.com). Updated at every deploy.
Red Hat Data Grid 8.6 is supported until December 31, 2027, its end-of-support date. Active support for Red Hat Data Grid 8.6 ends on December 31, 2026. It is also the next Red Hat Data Grid version to reach end of life. 8 of 9 tracked Red Hat Data Grid versions are past end of life; the most recent to reach it, 8.5, did so on September 17, 2026. The full Red Hat Data Grid lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 6 | — | Jul 1, 2012 | Jun 30, 2017 | Jun 30, 2021 Red Hat Extended Life Cycle Support (ended) |
3398 days past EOL | EOL |
| 7.3 | — | Feb 11, 2019 | Jul 21, 2021 | Jul 31, 2024 Red Hat Extended Life Cycle Support (ended) |
1916 days past EOL | EOL |
| 8.0 | — | Apr 1, 2020 | Mar 3, 2021 | — | 2056 days past EOL | EOL |
| 8.1 | — | Sep 3, 2020 | Nov 26, 2021 | — | 1788 days past EOL | EOL |
| 8.2 | — | May 26, 2021 | Aug 14, 2022 | — | 1527 days past EOL | EOL |
| 8.3 | — | Feb 14, 2022 | May 17, 2023 | — | 1251 days past EOL | EOL |
| 8.4 | — | Nov 17, 2022 | Dec 10, 2024 | — | 678 days past EOL | EOL |
| 8.5 | — | Jul 10, 2024 | Sep 17, 2026 | — | 32 days past EOL | EOL |
| 8.6 | — | Mar 16, 2026 | Dec 31, 2027 | Dec 31, 2030 Red Hat Extended Life Cycle Support |
438 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/redhat-data-grid)
Red Hat Data Grid lifecycle status — the real story
Red Hat Data Grid is Red Hat's supported distribution of the Infinispan in-memory data grid. Each 8.x minor gets Full support until the next minor and then a short Maintenance phase; 8.6 and 7.3 also have a paid ELS 1 add-on. ELS 2 phases are advice only and are not counted as extended support.
Red Hat Data Grid release and support pattern
Across the 9 release lines with a published release date, Red Hat Data Grid has shipped a new line roughly every 0.9 years (median interval). A line typically stays in standard support for about 1.8 years from its release to its standard-support end date.
Of the 9 release lines tracked, 8 are past end of life and 1 is still within support. The newest line, 8.6, was released March 16, 2026. The next scheduled end of life is 8.6 on December 31, 2027 — 437 days from this build. Upstream also publishes an extended-support phase for 3 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Red Hat Data Grid end of life mean for your organization?
When a version of Red Hat Data Grid 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Red Hat Data Grid 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 Red Hat Data Grid 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.
| Option | Best when | Watch 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.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Red Hat Data Grid version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Red Hat Data Grid has 8 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Red Hat Data Grid is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."