Rtpengine End of Life Dates

other

Rtpengine is a crucial tool for developers, created to manage and support various versions of the software, ensuring seamless transitions and minimizing potential security risks. Maintained by a team of dedicated experts, Rtpengine has been a go-to solution for tracking end-of-life dates, supported versions, and security patch timelines since its inception. Developers rely on Rtpengine to stay informed about the lifecycle of each release, allowing them to plan upgrades and migrations efficiently. With a total of 24 versions, Rtpengine provides comprehensive coverage, enabling developers to make informed decisions about their projects.

The end-of-life landscape for Rtpengine is characterized by a significant number of versions that have already reached their expiration date, with 20 out of 24 versions no longer supported. Currently, only four versions remain active, with the latest stable version being 11.5.1.52. Looking ahead, the next version to reach its end-of-life date is 11.5, scheduled for September 11, 2026. This information is vital for developers who need to plan their upgrades and ensure continuity. The most recent version to reach its end-of-life date was 14.1, which expired on May 1, 2026, underscoring the importance of staying up-to-date with the latest information.

From a security perspective, Rtpengine presents a clean slate, with no known CVEs tracked, and consequently, no critical CVEs. As a result, there is no most affected version, and the KEV status is not applicable. This positive security picture is a testament to the robustness of Rtpengine. Nevertheless, developers should remain vigilant and continue to monitor the software's lifecycle, ensuring they take prompt action when necessary. By staying informed about the latest developments and planned end-of-life dates, developers can minimize potential risks and ensure the continued security and integrity of their projects.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
26.2 Aug 31, 2026—Oct 31, 2026in 8d26.2.1.5—EOL soon
26.1 Jun 30, 2026—Aug 31, 202653d ago26.1.1.11—EOL
26.0 LTSMay 1, 2026—May 1, 2029in 921d26.0.1.26—Active
14.1 Feb 28, 2026—May 1, 2026175d ago14.1.1.21—EOL
14.0 Dec 17, 2025—Feb 28, 2026237d ago14.0.1.11—EOL
13.5 LTSSep 26, 2025—Sep 28, 2028in 706d13.5.1.30—Active
13.4 Jun 27, 2025—Sep 26, 2025392d ago13.4.1.10—EOL
13.3 May 14, 2025—Jun 27, 2025483d ago13.3.1.16—EOL
13.2 Feb 21, 2025—May 14, 2025527d ago13.2.1.16—EOL
13.1 Dec 20, 2024—Feb 21, 2025609d ago13.1.1.16—EOL
13.0 Nov 8, 2024—Dec 20, 2024672d ago13.0.1.10—EOL
12.5 LTSSep 20, 2024—Sep 24, 2027in 336d12.5.1.56—Active
12.4 May 31, 2024—Sep 20, 2024763d ago12.4.1.11—EOL
12.3 Apr 5, 2024—May 31, 2024875d ago12.3.1.6—EOL
12.2 Feb 9, 2024—Apr 5, 2024931d ago12.2.1.5—EOL
12.1 Dec 22, 2023—Feb 9, 2024987d ago12.1.1.7—EOL
12.0 Nov 3, 2023—Dec 22, 20231036d ago12.0.1.5—EOL
11.5 LTSSep 22, 2023—Sep 11, 202642d ago11.5.1.53—EOL
11.4 Jul 21, 2023—Sep 8, 20231141d ago11.4.1.8—EOL
11.3 Apr 14, 2023—Jul 21, 20231190d ago11.3.1.15—EOL
11.2 Feb 17, 2023—Apr 14, 20231288d ago11.2.1.12—EOL
11.1 Oct 28, 2022—Feb 17, 20231344d ago11.1.1.12—EOL
11.0 Sep 2, 2022—Oct 28, 20221456d ago11.0.1.7—EOL
10.5 LTSJul 8, 2022—Sep 5, 2025413d ago10.5.9.1—EOL
9.5 Jul 2, 2021—Sep 6, 2024777d ago9.5.9.1—EOL
8.5 Jul 31, 2020—Dec 8, 20231050d ago8.5.12.2—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions