Elixir End of Life Dates

language

Developers working with the Elixir language have a powerful tool at their disposal, one that has been refined over time since its creation. Maintained by a dedicated team, Elixir has become a go-to choice for building scalable and maintainable applications, thanks to its ability to handle concurrency and fault tolerance with ease. The language has garnered a strong following among developers due to its simplicity, flexibility, and performance, making it an ideal choice for a wide range of projects. With a history of continuous improvement, Elixir has evolved to meet the changing needs of the development community, with new versions being released regularly to address issues and add features.

The end-of-life landscape for Elixir is characterized by a total of 17 versions, with 12 of these having already reached their end-of-life. Currently, 5 versions remain active, with the latest stable version being 1.16.3. The most recent version to reach its end-of-life was 1.15, which occurred on 2026-06-03. Notably, there is no next scheduled end-of-life date announced, giving developers a degree of stability and predictability when planning their projects. This information is crucial for developers to ensure they are working with supported versions, thereby minimizing potential security risks and compatibility issues.

From a security standpoint, Elixir presents a clean slate, with a total of 0 CVEs tracked and no critical vulnerabilities reported. This robust security profile is a significant advantage for developers, as it means they can focus on building their applications without worrying about known security flaws. Given the absence of any reported vulnerabilities, there is no most affected version to be concerned about. Furthermore, with no known vulnerabilities, Elixir does not have a KEV status, allowing developers to proceed with confidence when using the language for their projects. As a result, developers can take action by ensuring they keep their Elixir installations up to date with the latest stable version to maintain the highest level of security and stability.

Last updated: Jul 24, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
1.20 Jun 3, 2026No1.20.2Active
1.19 Oct 16, 2025Jun 3, 2026No1.19.5Active
1.18 Dec 19, 2024Oct 16, 2025No1.18.4Active
1.17 Jun 12, 2024Dec 19, 2024No1.17.3Active
1.16 Dec 22, 2023Jun 12, 2024No1.16.3Active
1.15 Jun 19, 2023Dec 22, 2023Jun 3, 202651d ago1.15.8EOL
1.14 Sep 1, 2022Jun 19, 2023Oct 16, 2025281d ago1.14.5EOL
1.13 Dec 3, 2021Sep 1, 2022Dec 19, 2024582d ago1.13.4EOL
1.12 May 19, 2021Dec 3, 2021Jun 12, 2024772d ago1.12.3EOL
1.11 Oct 6, 2020May 19, 2021Dec 22, 2023945d ago1.11.4EOL
1.10 Jan 27, 2020Oct 6, 2020Jun 19, 20231131d ago1.10.4EOL
1.9 Jun 24, 2019Jan 27, 2020Sep 1, 20221422d ago1.9.4EOL
1.8 Jan 14, 2019Jun 24, 2019Dec 3, 20211694d ago1.8.2EOL
1.7 Jul 25, 2018Jan 14, 2019May 19, 20211892d ago1.7.4EOL
1.6 Jan 17, 2018Jul 25, 2018Oct 6, 20202117d ago1.6.6EOL
1.5 Jul 25, 2017Jan 17, 2018Jan 27, 20202370d ago1.5.3EOL
1.4 Jan 5, 2017Jul 25, 2017Jun 24, 20192587d ago1.4.5EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions