endoflife.ai
Erlang Erlang/OTP 27 Erlang/OTP 29 EOL Checker

Erlang/OTP 27 End of Life: Supported Until OTP 30 Is Released

By Scott Bissett  ·  Published: November 21, 2026  ·  Reference guide  ·  Policy wording read on the day of publication from the security policy in the erlang/otp repository and from the Erlang/OTP documentation on erlang.org.

Erlang/OTP 27 has no end-of-life date announced by the Erlang/OTP project: the project's security policy supports the last 3 OTP releases, so OTP 27 is supported now and leaves the supported set when OTP 30 is released. OTP 29 is the latest release, which makes the three supported releases OTP 29, OTP 28 and OTP 27. This site lists May 20, 2027 as the projected end of life for OTP 27. The project has not printed that date. It follows from the policy and from the pattern of one major release each May, and it moves if OTP 30 arrives earlier or later.

Quick answer: No end-of-life date has been announced for Erlang/OTP 27. The security policy in the erlang/otp repository reads: "Erlang/OTP supports the last 3 OTP releases with security updates and patches." OTP 27 is the oldest of those three today. It stops being one of them on the day OTP 30 is released, a day the project has not announced.

Key Dates at a Glance

Running Erlang/OTP past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers Erlang/OTP is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

Erlang/OTP releases under the security policy

ReleaseReleasedUnder the security policyEnd of life on this site
Erlang/OTP 29May 11, 2026Supported, latest releaseMay 11, 2029, projected
Erlang/OTP 28May 20, 2025SupportedMay 20, 2028, projected
Erlang/OTP 27May 17, 2024Supported, oldest of the threeMay 20, 2027, projected
Erlang/OTP 26May 15, 2023Not supported since OTP 29May 26, 2026, the date of its newest patch

The third column applies the project's rule of the last 3 OTP releases to the releases that exist today. The project prints no end-of-life dates. The dates in the last column are this site's: projections for the three supported releases, and for OTP 26 the date of the newest patch in our records. Release dates are the dates of the OTP-29.0, OTP-28.0, OTP-27.0 and OTP-26.0 tags in the erlang/otp repository; the announcements on erlang.org are dated within three days of them. Older releases are on our Erlang page.

What the Erlang/OTP project says about support

The project describes support in three places. None of them gives a calendar date for the end of a release.

Read together: new features and routine bug fixes go to the latest release, OTP 29. OTP 28 and OTP 27 are covered by the security policy and receive patches on their maint branches. The newest OTP 27 patch in our records is dated October 14, 2026.

Where the projected date comes from

The policy counts releases, not years. OTP 27 stays in the supported set until one more major release exists. That release is OTP 30, and the project has announced no date for it.

The release history shows a steady pattern. OTP 26 was released on May 15, 2023, OTP 27 on May 17, 2024, OTP 28 on May 20, 2025 and OTP 29 on May 11, 2026: one major release each May. If OTP 30 follows the pattern, it arrives about a year after OTP 29, and OTP 27 leaves the supported set then. May 20, 2027 is this site's projection of that day. Treat it as a planning date, not as a commitment by the project.

OTP 26 shows how the change looks in practice. It was the oldest of the three supported releases until OTP 29 was released on May 11, 2026. The newest OTP 26 patch in our records is dated May 26, 2026, shortly after that release. That fits the project's statement that fixes made on older releases are made available as well.

Why the supported set matters: CVE-2025-32433

Erlang/OTP is in CISA's Known Exploited Vulnerabilities catalog. CISA added CVE-2025-32433 on June 9, 2025, with a remediation due date of June 30, 2025 for federal agencies. The flaw is in the Erlang/OTP SSH server and allows unauthenticated remote code execution.

The project's security advisory lists every OTP version from 17.0 as affected and three patched versions: 27.3.3, 26.2.5.11 and 25.3.2.20. OTP 27 was the latest release at the time, so those are the last 3 OTP releases of that day. The advisory lists no patched version for OTP 24 or older. Its other guidance is a temporary workaround until an upgrade: disable the SSH server or block access to it with firewall rules.

That is the practical meaning of the policy. In this case each release inside the last three got a patched version, and the advisory names none for the releases outside it.

What an Erlang/OTP 27 owner should plan

  1. Stay on the newest OTP 27 patch. OTP 27 is supported today, and its fixes arrive as patch packages on the 27 line. Our Erlang/OTP 27 page shows the newest patch we have on record.
  2. Choose a target: OTP 28 or OTP 29. Both are inside the supported set and will still be inside it after OTP 30 is released.
  3. Use the compatibility window. The Erlang/OTP documentation says Erlang nodes can communicate across at least two preceding and two subsequent releases, and that compiled code can be loaded on at least two subsequent releases. An OTP 27 node can therefore run in a cluster with OTP 28 and OTP 29 nodes during a rolling upgrade. The documentation also says loading code on a previous release is not supported, and recommends compiling with the release the code is deployed on.
  4. Check what runs on top. Products built on Erlang/OTP set their own supported OTP range. RabbitMQ, for example, publishes a minimum required and a maximum supported Erlang/OTP version for each of its releases. Confirm the target OTP release is inside that range before moving.
  5. Watch for OTP 30. Release candidates are announced on the News page of erlang.org ahead of each major release. The first release candidate of OTP 30 is the signal that OTP 27's time in the supported set is ending.
  6. On OTP 26 or older: those releases are outside the last three. Move to a supported release first.

The EOL Checker looks up one product and version. The Stack Scanner reads a dependency file and reports the end-of-life dates of the components it recognizes.

Frequently Asked Questions

When does Erlang/OTP 27 reach end of life?

The Erlang/OTP project has not announced an end-of-life date for OTP 27. Its security policy supports the last 3 OTP releases with security updates and patches. OTP 29 is the latest release, so OTP 27 is the oldest supported release and leaves the supported set when OTP 30 is released. This site's projected date for that is May 20, 2027, which follows from the policy and the yearly release pattern and is not a date the project has printed.

Is Erlang/OTP 27 still supported?

Yes. The security policy in the erlang/otp repository supports the last 3 OTP releases. With OTP 29 as the latest release, those are OTP 29, OTP 28 and OTP 27.

Is Erlang/OTP 26 still supported?

No, not under the security policy. OTP 26 fell outside the last 3 OTP releases when OTP 29 was released. Our records date that release May 11, 2026.

What is the latest Erlang/OTP release?

OTP 29. It is the newest of the three supported releases, ahead of OTP 28 and OTP 27. Our records date its release May 11, 2026.

Does Erlang/OTP 27 still get bug fixes?

The security policy covers it with maintenance and security releases. The project's documentation adds that, in general, bugs are only fixed on the latest release, and that fixes made on older releases are made available and announced as well. The newest OTP 27 patch in our records is dated October 14, 2026.

Has Erlang/OTP been in the CISA Known Exploited Vulnerabilities catalog?

Yes. CISA added CVE-2025-32433, an unauthenticated remote code execution flaw in the Erlang/OTP SSH server, to the catalog on June 9, 2025. The project's advisory lists patched versions for OTP 27, OTP 26 and OTP 25, the three releases supported at that time.

Related

© 2026 endoflife.ai · How we verify our dates · API · About