Erlang 22 · Version Status
Erlang 22 End of Life Date
Erlang 22 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 22 is past end of life. This version no longer receives security patches. 919 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 18, 2024
919 days past EOL
Latest Release
22.3.4.27
Standard release
Release Date
May 10, 2019
Erlang 22 series
Lifecycle detail
Erlang 22 was released on May 10, 2019 and support ended on March 18, 2024 — a supported lifespan of 4 years and 10 months, longer than the 3 years median for Erlang releases. The last patch it will ever receive is 22.3.4.27, published March 18, 2024 — on the day support ended. It has been without security patches for 2 years and 6 months. 3 newer Erlang releases have shipped since.
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 22 support is available
Commercial vendors offer security patches beyond EOL. 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 22 end of life mean?
When Erlang 22 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 22 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 22 reach end of life?
Erlang 22 reached end of life on March 18, 2024. This version is no longer receiving security patches.
Is Erlang 22 still supported?
No. Erlang 22 reached end of life on March 18, 2024 and is no longer receiving security patches.
What should I upgrade to from Erlang 22?
The recommended upgrade from Erlang 22 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 22 past EOL?
When Erlang 22 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.