Elixir End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Elixir versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.4 | 1.4.5 | Jan 5, 2017 | Jun 24, 2019 | 2576 days past EOL | EOL |
| 1.5 | 1.5.3 | Jul 25, 2017 | Jan 27, 2020 | 2359 days past EOL | EOL |
| 1.6 | 1.6.6 | Jan 17, 2018 | Oct 6, 2020 | 2106 days past EOL | EOL |
| 1.7 | 1.7.4 | Jul 25, 2018 | May 19, 2021 | 1881 days past EOL | EOL |
| 1.8 | 1.8.2 | Jan 14, 2019 | Dec 3, 2021 | 1683 days past EOL | EOL |
| 1.9 | 1.9.4 | Jun 24, 2019 | Sep 1, 2022 | 1411 days past EOL | EOL |
| 1.10 | 1.10.4 | Jan 27, 2020 | Jun 19, 2023 | 1120 days past EOL | EOL |
| 1.11 | 1.11.4 | Oct 6, 2020 | Dec 22, 2023 | 934 days past EOL | EOL |
| 1.12 | 1.12.3 | May 19, 2021 | Jun 12, 2024 | 761 days past EOL | EOL |
| 1.13 | 1.13.4 | Dec 3, 2021 | Dec 19, 2024 | 571 days past EOL | EOL |
| 1.14 | 1.14.5 | Sep 1, 2022 | Oct 16, 2025 | 270 days past EOL | EOL |
| 1.15 | 1.15.8 | Jun 19, 2023 | Jun 3, 2026 | 40 days past EOL | EOL |
| 1.16 | 1.16.3 | Dec 22, 2023 | TBD | Supported | Active |
| 1.17 | 1.17.3 | Jun 12, 2024 | TBD | Supported | Active |
| 1.18 | 1.18.4 | Dec 19, 2024 | TBD | Supported | Active |
| 1.19 | 1.19.5 | Oct 16, 2025 | TBD | Supported | Active |
| 1.20 | 1.20.2 | Jun 3, 2026 | TBD | Supported | Active |
What does Elixir end of life mean for your organization?
When a version of Elixir 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 Elixir 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 Elixir versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Elixir has 12 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →