Unsupported Software Findernotice of vendor support

Erlang end of life dates

The support dates the endoflife.date record (community-maintained) holds for Erlang, read on 28 Oct 2026: when security support ends for each version (cycle), when active support ends, and extended support where the record shows it. Below them, what Cyber Essentials, the Essential Eight, CIS Controls v8, PCI DSS and NIST SP 800-53 ask of a version past its end.

Which Erlang versions are no longer supported?

On 28 Oct 2026, 10 of the 13 Erlang versions in the endoflife.date record are past vendor security support, the most recent being Erlang 26, Erlang 25 and Erlang 24. 3 are still supported, the newest being Erlang 29, Erlang 28 and Erlang 27.

How long will current Erlang versions be supported?

The next to lose security support is Erlang 27, on 20 May 2027, then Erlang 28 on 20 May 2028 and Erlang 29 on 11 May 2029. Dates from the endoflife.date record, read 28 Oct 2026; the vendor notice is authoritative.

How many Erlang versions are there?

The endoflife.date record holds 13 Erlang versions, from Erlang 17, released 7 Apr 2014, to Erlang 29, released 11 May 2026, read 28 Oct 2026.

Last updated: 2026-10-28. Every date on this page is the record's own, read 28 Oct 2026.

Oldest version still in support
27, security support to 20 May 2027
Next end date
27, security support ends 20 May 2027
Vendor's own notice
the vendor lifecycle policy for Erlang, authoritative; each version below links its own notice where the record carries one
Record
Erlang
Kind
language runtime
Versions in the record
13
Versions past vendor support
10
Essential Eight class
an application outside the priority classes: ISM-0304 asks for its removal at ML3 only; at ML1 and ML2 no Essential Eight clause here turns on it
Source
endoflife.date/erlang, community-maintained, MIT licence, read 28 Oct 2026; sources

Erlang versions and their support dates

as at 28 Oct 2026
CycleReleasedActive support endsSecurity support endsExtended support endsOn the read dateVendor notice
2911 May 2026ended, date not published11 May 2029none in the recordsupportednone in the record
2820 May 202511 May 202620 May 2028none in the recordsecurity fixes onlynone in the record
2717 May 202420 May 202520 May 2027none in the recordsecurity fixes onlynone in the record
2615 May 202317 May 202426 May 2026none in the recordpast vendor supportnone in the record
2517 May 202215 May 202317 May 2025none in the recordpast vendor supportnone in the record
2410 May 202117 May 202210 May 2024none in the recordpast vendor supportnone in the record
2311 May 202010 May 202114 Mar 2024none in the recordpast vendor supportnone in the record
2210 May 201911 May 202018 Mar 2024none in the recordpast vendor supportnone in the record
2119 Jun 201810 May 201919 Jun 2021none in the recordpast vendor supportnone in the record
2021 Jun 201719 Jun 201821 Jun 2020none in the recordpast vendor supportnone in the record
1921 Jun 201621 Jun 201721 Jun 2019none in the recordpast vendor supportnone in the record
1823 Jun 201521 Jun 20169 Nov 2018none in the recordpast vendor supportnone in the record
177 Apr 201423 Jun 201511 Oct 2018none in the recordpast vendor supportnone in the record

A version this table does not list is not in the record: the finder reads it as unknown, never supported. The dates are the record's own; nothing here states a date the record does not hold.

What the schemes ask of a version past its end

Cyber Essentials
software on in-scope devices licensed and supported by the vendor, meaning it still receives security updates; unsupported software removed or segregated (SU.1, SU.4). Cyber Essentials Plus: removed, or isolated with compensating controls (PM-02).
Essential Eight
An application outside the priority classes: ISM-0304 asks for its removal at ML3 only; at ML1 and ML2 no Essential Eight clause here turns on it
CIS Controls v8, Safeguard 2.2
only software that still receives vendor support may be marked authorised; unsupported software kept for the mission needs a recorded exception with compensating controls and the acceptance of the remaining risk; support status checked at least monthly.
PCI DSS 12.3.4
hardware and software reviewed at least every 12 months: that vendors still supply timely security fixes, end-of-life announcements documented, and a remediation plan for outdated technology approved by senior management.
NIST SP 800-53 SA-22
system components replaced when support is no longer available from the developer, vendor or manufacturer, or alternative sources of continued support provided.

See the specimen list runCheck your own list

Is my Erlang version still supported?

One line per version in the record, newest first, on 28 Oct 2026. Link to a line with its own address.