Erlang 17 · Version Status
Erlang 17 End of Life Date
Erlang 17 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Erlang 17 is past end of life. This version no longer receives security patches. 2767 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 11, 2018
2767 days past EOL
Latest Release
17.5.6.10
Standard release
Release Date
Apr 7, 2014
Erlang 17 series
| Version | Latest | EOL Date | Status |
|---|
| → 17 |
17.5.6.10 |
Oct 11, 2018 |
EOL |
| 18 |
18.3.4.11 |
Nov 9, 2018 |
EOL |
| 19 |
19.3.6.13 |
Jun 21, 2019 |
EOL |
| 20 |
20.3.8.26 |
Jun 21, 2020 |
EOL |
| 21 |
21.3.8.24 |
Jun 19, 2021 |
EOL |
| 22 |
22.3.4.27 |
May 10, 2022 |
EOL |
| 23 |
23.3.4.20 |
Jun 5, 2023 |
EOL |
| 24 |
24.3.4.17 |
May 10, 2024 |
EOL |
What does Erlang 17 end of life mean?
When Erlang 17 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Erlang 17 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Erlang 28 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Erlang 17 reach end of life?
Erlang 17 reached end of life on October 11, 2018. This version is no longer receiving security patches.
Is Erlang 17 still supported?
No. Erlang 17 reached end of life on October 11, 2018 and is no longer receiving security patches.
What should I upgrade to from Erlang 17?
The recommended upgrade from Erlang 17 is
Erlang 28 — the latest actively supported version. Check the
Erlang full timeline for all supported versions.
What are the security risks of running Erlang 17 past EOL?
When Erlang 17 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Erlang should migrate immediately or implement compensating controls.