rtpengine 10.5 · Version Status
rtpengine 10.5 End of Life Date
rtpengine 10.5 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.
⚠
rtpengine 10.5 is past end of life. This version no longer receives security patches. 370 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 5, 2025
370 days past EOL
Latest Release
10.5.9.1
LTS release
Release Date
Jul 8, 2022
rtpengine 10.5 series
Lifecycle detail
rtpengine 10.5 was released on July 8, 2022 and support ended on September 5, 2025 — a supported lifespan of 3 years and 2 months, in line with the 3 years median for rtpengine LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. The last patch it will ever receive is 10.5.9.1, published July 29, 2025 — 38 days before support ended. It has been without security patches for 1 year. 6 newer rtpengine releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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 rtpengine 10.5 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 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 10.5 end of life mean?
When rtpengine 10.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 10.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 10.5 reach end of life?
rtpengine 10.5 reached end of life on September 5, 2025. This version is no longer receiving security patches.
Is rtpengine 10.5 still supported?
No. rtpengine 10.5 reached end of life on September 5, 2025 and is no longer receiving security patches.
What should I upgrade to from rtpengine 10.5?
The recommended upgrade from rtpengine 10.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 10.5 past EOL?
When rtpengine 10.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.