Erlang End of Life Dates

language

Developers working with concurrent and functional programming languages often require a reliable and efficient solution to build scalable systems. Erlang, a general-purpose language created to support such development, has been a cornerstone of the programming landscape since its inception. The language is maintained by the Erlang/OTP team at Ericsson, and its open-source nature has made it a favorite among developers who need a high-level language with a garbage-collected runtime system. With its origins dating back to the 1980s, Erlang has evolved to become a crucial tool for developers seeking to build fault-tolerant and concurrent systems.

The Erlang ecosystem comprises 13 versions, with 10 of these versions having reached their end-of-life status. Currently, only 3 versions remain active, with the latest stable version being 27.3.4.13. The landscape of Erlang's end-of-life versions is set to change, as version 27 is scheduled to expire on 2027-05-20. This follows the expiration of version 26, which occurred on 2026-05-26. As the ecosystem continues to evolve, developers must remain vigilant about the status of the versions they are using to ensure they receive necessary updates and support.

Given the current security landscape, Erlang has a pristine record with 0 tracked CVEs, and consequently, 0 critical CVEs. As a result, there is no most affected version, and the Known Exploited Vulnerabilities catalog does not apply to Erlang. This exemplary security record is a testament to the language's robust design and the dedication of its maintainers. Developers using Erlang can continue to build their systems with confidence, but it is essential to keep their versions up to date to ensure they remain supported and secure. By staying informed about the latest developments and version updates, developers can harness the full potential of Erlang to build scalable, fault-tolerant, and secure systems.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
29 May 11, 2026—May 11, 2029in 931d29.1.2—Active
28 May 20, 2025May 11, 2026May 20, 2028in 575d28.5.0.8—Active
27 May 17, 2024May 20, 2025May 20, 2027in 209d27.3.4.19—Active
26 May 15, 2023May 17, 2024May 26, 2026150d ago26.2.5.21—EOL
25 May 17, 2022May 15, 2023May 17, 2025524d ago25.3.2.21—EOL
24 May 10, 2021May 17, 2022May 10, 2024896d ago24.3.4.17—EOL
23 May 11, 2020May 10, 2021Mar 14, 2024953d ago23.3.4.20—EOL
22 May 10, 2019May 11, 2020Mar 18, 2024949d ago22.3.4.27—EOL
21 Jun 19, 2018May 10, 2019Jun 19, 20211952d ago21.3.8.24—EOL
20 Jun 21, 2017Jun 19, 2018Jun 21, 20202315d ago20.3.8.26—EOL
19 Jun 21, 2016Jun 21, 2017Jun 21, 20192681d ago19.3.6.13—EOL
18 Jun 23, 2015Jun 21, 2016Nov 9, 20182905d ago18.3.4.11—EOL
17 Apr 7, 2014Jun 23, 2015Oct 11, 20182934d ago17.5.6.10—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions