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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 20.1 | 20.1.0.4 | Aug 11, 2020 | Apr 20, 2021 | 1890 days past EOL | EOL |
| 20.2 | 20.2.0.0 | Oct 26, 2020 | Jan 8, 2021 | 1992 days past EOL | EOL |
| 20.3 LTS | 20.3.3.0 | Jan 8, 2021 | Oct 19, 2021 | 1708 days past EOL | EOL |
| 21.0 | 21.0.0.0 | Feb 1, 2021 | Apr 26, 2021 | 1884 days past EOL | EOL |
| 21.1 | 21.1.0.0 | Apr 26, 2021 | Jul 20, 2021 | 1799 days past EOL | EOL |
| 21.2 LTS | 21.2.0.2 | Jul 21, 2021 | Jan 18, 2022 | 1617 days past EOL | EOL |
| 21.3 LTS | 21.3.6.0 | Oct 20, 2021 | Jul 17, 2023 | 1072 days past EOL | EOL |
| 22.0 | 22.0.0.2 | Jan 26, 2022 | Apr 26, 2022 | 1519 days past EOL | EOL |
| 22.1 | 22.1.0.0 | Apr 27, 2022 | Jul 26, 2022 | 1428 days past EOL | EOL |
| 22.2 | 22.2.0.0 | Jul 27, 2022 | Oct 25, 2022 | 1337 days past EOL | EOL |
| 22.3 LTS | 22.3.5.0 | Nov 2, 2022 | Apr 17, 2024 | 797 days past EOL | EOL |
| 23.0 LTS | 23.0.6.0 | Jun 14, 2023 | Jan 21, 2025 | 518 days past EOL | EOL |
| 23.1 LTS | 23.1.11.0 | Oct 12, 2023 | TBD | Supported | Active |
| 24.0 | 24.0.2.0 | Mar 27, 2024 | Oct 15, 2024 | 616 days past EOL | EOL |
| 24.1 | 24.1.2.0 | Sep 23, 2024 | Apr 15, 2025 | 434 days past EOL | EOL |
| 24.2 | 24.2.2.0 | Mar 25, 2025 | Oct 21, 2025 | 245 days past EOL | EOL |
| 25.0 LTS | 25.0.3.0 | Oct 2, 2025 | TBD | Supported | Active |
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: 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 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.
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.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →