Erlang 28 · Version Status

Erlang 28 End of Life Date

Erlang 28 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

✓ Erlang 28 is actively supported. EOL date: May 20, 2028.
📅 Get reminded before Erlang 28 reaches EOL on May 20, 2028 — alerts 90, 30 & 7 days out.
Google →
EOL Date
May 20, 2028
650 days remaining
Latest Release
28.5.0.5
Standard release
Release Date
May 20, 2025
Erlang 28 series
Lifecycle detail

Erlang 28 was released on May 20, 2025 and support is scheduled to end on May 20, 2028 — a planned supported lifespan of 3 years, in line with the 3 years median for Erlang releases. Its most recent patch is 28.5.0.5, published August 3, 2026.

← Erlang 27 All Erlang versions Erlang 29 →
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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 →
All Erlang Versions
VersionLatestEOL DateStatus
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 28 end of life mean?

When Erlang 28 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 28 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Erlang 29 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Erlang 28 reach end of life?
Erlang 28 reached end of life on May 20, 2028. That is 650 days remaining.
Is Erlang 28 still supported?
Yes, Erlang 28 is currently supported. The EOL date is May 20, 2028.
What should I upgrade to from Erlang 28?
The recommended upgrade from Erlang 28 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 28 past EOL?
When Erlang 28 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.
Data from endoflife.date API · Generated at build time · How we source data →