Mandrel End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Mandrel versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Mandrel 25.0 (JDK 25) is supported, with no end-of-life or end-of-support date announced yet. 15 of 17 tracked Mandrel versions are past end of life; the most recent to reach it, 24.2 (JDK 24), did so on October 21, 2025. The full Mandrel 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 | Days | Status |
|---|---|---|---|---|---|
| 20.1 (JDK 11) | 20.1.0.4 | Aug 11, 2020 | Apr 20, 2021 | 1982 days past EOL | EOL |
| 20.2 (JDK 11) | 20.2.0.0 | Oct 26, 2020 | Jan 8, 2021 | 2084 days past EOL | EOL |
| 20.3 (JDK 11) LTS | 20.3.3.0 | Jan 8, 2021 | Oct 19, 2021 | 1800 days past EOL | EOL |
| 21.0 (JDK 11) | 21.0.0.0 | Feb 1, 2021 | Apr 26, 2021 | 1976 days past EOL | EOL |
| 21.1 (JDK 11) | 21.1.0.0 | Apr 26, 2021 | Jul 20, 2021 | 1891 days past EOL | EOL |
| 21.2 (JDK 11) LTS | 21.2.0.2 | Jul 21, 2021 | Jan 18, 2022 | 1709 days past EOL | EOL |
| 21.3 (JDK 11, JDK 17) LTS | 21.3.6.0 | Oct 20, 2021 | Jul 17, 2023 | 1164 days past EOL | EOL |
| 22.1 (JDK 11, JDK 17) | 22.0.0.2 | Jan 26, 2022 | Apr 26, 2022 | 1611 days past EOL | EOL |
| 22.1 (JDK 11, JDK 17) | 22.1.0.0 | Apr 27, 2022 | Jul 26, 2022 | 1520 days past EOL | EOL |
| 22.2 (JDK 11, JDK 17) | 22.2.0.0 | Jul 27, 2022 | Oct 25, 2022 | 1429 days past EOL | EOL |
| 22.3 (JDK 17) LTS | 22.3.5.0 | Nov 2, 2022 | Apr 17, 2024 | 889 days past EOL | EOL |
| 23.0 (JDK 17) LTS | 23.0.6.0 | Jun 14, 2023 | Jan 21, 2025 | 610 days past EOL | EOL |
| 23.1 (JDK 21) LTS | 23.1.12.1 | Oct 12, 2023 | TBD | Supported | Active |
| 24.0 (JDK 22) | 24.0.2.0 | Mar 27, 2024 | Oct 15, 2024 | 708 days past EOL | EOL |
| 24.1 (JDK 23) | 24.1.2.0 | Sep 23, 2024 | Apr 15, 2025 | 526 days past EOL | EOL |
| 24.2 (JDK 24) | 24.2.2.0 | Mar 25, 2025 | Oct 21, 2025 | 337 days past EOL | EOL |
| 25.0 (JDK 25) LTS | 25.0.4.1 | Oct 2, 2025 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/mandrel)
Mandrel release and support pattern
Across the 17 release lines with a published release date, Mandrel has shipped a new line roughly every 3 months (median interval). A line typically stays supported for about 7 months from its release to its end-of-life date (measured on the 15 lines with both dates published). 7 of the 17 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 17 release lines tracked, 15 are past end of life and 2 are still within support. The newest line, 25.0, was released October 2, 2025. No end-of-life date is currently published for the 2 supported lines.
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 Mandrel end of life mean for your organization?
When a version of Mandrel 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 Mandrel 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 Mandrel 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, extended support vendors provide continued security patches for EOL Mandrel versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Mandrel has 15 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 Mandrel 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."