Complete end-of-life dates, support windows, and security status for all Erlang versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 17 | 17.5.6.10 | Apr 7, 2014 | Oct 11, 2018 | 2767 days past EOL | EOL |
| 18 | 18.3.4.11 | Jun 23, 2015 | Nov 9, 2018 | 2738 days past EOL | EOL |
| 19 | 19.3.6.13 | Jun 21, 2016 | Jun 21, 2019 | 2514 days past EOL | EOL |
| 20 | 20.3.8.26 | Jun 21, 2017 | Jun 21, 2020 | 2148 days past EOL | EOL |
| 21 | 21.3.8.24 | Jun 19, 2018 | Jun 19, 2021 | 1785 days past EOL | EOL |
| 22 | 22.3.4.27 | May 10, 2019 | May 10, 2022 | 1460 days past EOL | EOL |
| 23 | 23.3.4.20 | May 11, 2020 | Jun 5, 2023 | 1069 days past EOL | EOL |
| 24 | 24.3.4.17 | May 10, 2021 | May 10, 2024 | 729 days past EOL | EOL |
| 25 | 25.3.2.21 | May 17, 2022 | May 17, 2025 | 357 days past EOL | EOL |
| 26 | 26.2.5.20 | May 15, 2023 | May 15, 2026 | 6 days remaining | Warning |
| 27 | 27.3.4.11 | May 17, 2024 | May 20, 2027 | 376 days remaining | Active |
| 28 | 28.5 | May 20, 2025 | May 20, 2028 | 742 days remaining | Active |
When a Erlang version 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 Erlang 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →