Rtpengine 13.5 · Version Status

Rtpengine 13.5 End of Life Date

Rtpengine 13.5 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Rtpengine 13.5 is actively supported. EOL date: September 28, 2028.
EOL Date
Sep 28, 2028
873 days remaining
Latest Release
13.5.1.10
LTS release
Release Date
Sep 26, 2025
Rtpengine 13.5 series
← Rtpengine 13.4 All Rtpengine versions Rtpengine 14.0 →
All Rtpengine Versions
VersionLatestEOL DateStatus
8.5 8.5.12.2 Dec 8, 2023 EOL
9.5 9.5.9.1 Sep 6, 2024 EOL
10.5 LTS 10.5.9.1 Sep 5, 2025 EOL
11.0 11.0.1.7 Oct 28, 2022 EOL
11.1 11.1.1.12 Feb 17, 2023 EOL
11.2 11.2.1.12 Apr 14, 2023 EOL
11.3 11.3.1.15 Jul 21, 2023 EOL
11.4 11.4.1.8 Sep 8, 2023 EOL

What does Rtpengine 13.5 end of life mean?

When Rtpengine 13.5 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Rtpengine 13.5 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Rtpengine 26.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Rtpengine 13.5 reach end of life?
Rtpengine 13.5 reached end of life on September 28, 2028. That is 873 days remaining.
Is Rtpengine 13.5 still supported?
Yes, Rtpengine 13.5 is currently supported. The EOL date is September 28, 2028.
What should I upgrade to from Rtpengine 13.5?
The recommended upgrade from Rtpengine 13.5 is Rtpengine 26.0 — the latest actively supported version. Check the Rtpengine full timeline for all supported versions.
What are the security risks of running Rtpengine 13.5 past EOL?
When Rtpengine 13.5 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Rtpengine should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →