Erlang 26 · Version Status
Erlang 26 End of Life Date
Erlang 26 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 26 is past end of life. This version no longer receives security patches. 165 days past EOL — migrate to a supported version immediately.
EOL Date
May 26, 2026
165 days past EOL
Latest Release
26.2.5.21
Standard release
Release Date
May 15, 2023
Erlang 26 series
Where these dates come from
End of lifeMay 26, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportMay 17, 2024endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseMay 15, 2023endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Erlang 26 was released on May 15, 2023 and support ended on May 26, 2026 — a supported lifespan of 3 years, in line with the 3 years median for Erlang releases. Its latest release on record is 26.2.5.21, published May 26, 2026 — on the day support ended. It has been past its end-of-life date for 6 months.
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 →
Extended Support
Extended Erlang 26 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| 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 26 end of life mean?
When Erlang 26 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 26 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 26 reach end of life?
Erlang 26 reached end of life on May 26, 2026. This version is no longer receiving security patches.
Is Erlang 26 still supported?
No. Erlang 26 reached end of life on May 26, 2026 and is no longer receiving security patches.
What should I upgrade to from Erlang 26?
The recommended upgrade from Erlang 26 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 26 past EOL?
Since Erlang 26 reached end of life, the maintainers no longer issue 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.