Erlang 27 · Version Status
Erlang 27 End of Life Date
Erlang 27 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Erlang 27 is actively supported. EOL date: May 20, 2027.
📅 Get reminded before Erlang 27 reaches EOL on May 20, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
May 20, 2027
239 days remaining
Latest Release
27.3.4.18
Standard release
Release Date
May 17, 2024
Erlang 27 series
Lifecycle detail
Erlang 27 was released on May 17, 2024 and support is scheduled to end on May 20, 2027 — a planned supported lifespan of 3 years, in line with the 3 years median for Erlang releases. Its most recent patch is 27.3.4.18, published September 21, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
| 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 |
Mar 18, 2024 |
EOL |
| 23 |
23.3.4.20 |
Mar 14, 2024 |
EOL |
| 24 |
24.3.4.17 |
May 10, 2024 |
EOL |
What does Erlang 27 end of life mean?
When Erlang 27 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Erlang 27 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Erlang 29 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Erlang 27 reach end of life?
Erlang 27 reached end of life on May 20, 2027. That is 239 days remaining.
Is Erlang 27 still supported?
Yes, Erlang 27 is currently supported. The EOL date is May 20, 2027.
What should I upgrade to from Erlang 27?
The recommended upgrade from Erlang 27 is
Erlang 29 — the latest actively supported version. Check the
Erlang full timeline for all supported versions.
What are the security risks of running Erlang 27 past EOL?
When Erlang 27 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Erlang should migrate immediately or implement compensating controls.