Envoy End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Envoy versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.0 | Sep 12, 2016 | Nov 30, 2016 | 3539 days past EOL | EOL |
| 1.1 | 1.1.0 | Nov 30, 2016 | Mar 7, 2017 | 3442 days past EOL | EOL |
| 1.2 | 1.2.0 | Mar 7, 2017 | May 17, 2017 | 3371 days past EOL | EOL |
| 1.3 | 1.3.0 | May 17, 2017 | Aug 24, 2017 | 3272 days past EOL | EOL |
| 1.4 | 1.4.0 | Aug 24, 2017 | Dec 4, 2017 | 3170 days past EOL | EOL |
| 1.5 | 1.5.0 | Dec 4, 2017 | Mar 20, 2018 | 3064 days past EOL | EOL |
| 1.6 | 1.6.0 | Mar 20, 2018 | Jun 21, 2018 | 2971 days past EOL | EOL |
| 1.7 | 1.7.1 | Jun 21, 2018 | Oct 4, 2018 | 2866 days past EOL | EOL |
| 1.8 | 1.8.0 | Oct 4, 2018 | Dec 20, 2018 | 2789 days past EOL | EOL |
| 1.9 | 1.9.1 | Dec 20, 2018 | Apr 5, 2019 | 2683 days past EOL | EOL |
| 1.10 | 1.10.0 | Apr 5, 2019 | Jul 11, 2019 | 2586 days past EOL | EOL |
| 1.11 | 1.11.2 | Jul 11, 2019 | Oct 31, 2019 | 2474 days past EOL | EOL |
| 1.12 | 1.12.7 | Oct 31, 2019 | Oct 31, 2020 | 2108 days past EOL | EOL |
| 1.13 | 1.13.8 | Jan 20, 2020 | Jan 20, 2021 | 2027 days past EOL | EOL |
| 1.14 | 1.14.7 | Apr 8, 2020 | Apr 8, 2021 | 1949 days past EOL | EOL |
| 1.15 | 1.15.5 | Jul 7, 2020 | Jul 7, 2021 | 1859 days past EOL | EOL |
| 1.16 | 1.16.5 | Oct 8, 2020 | Oct 8, 2021 | 1766 days past EOL | EOL |
| 1.17 | 1.17.4 | Jan 11, 2021 | Jan 11, 2022 | 1671 days past EOL | EOL |
| 1.18 | 1.18.6 | Apr 15, 2021 | Apr 15, 2022 | 1577 days past EOL | EOL |
| 1.19 | 1.19.5 | Jul 13, 2021 | Jul 13, 2022 | 1488 days past EOL | EOL |
| 1.20 | 1.20.7 | Oct 5, 2021 | Oct 5, 2022 | 1404 days past EOL | EOL |
| 1.21 | 1.21.6 | Jan 12, 2022 | Jan 12, 2023 | 1305 days past EOL | EOL |
| 1.22 | 1.22.11 | Apr 15, 2022 | Apr 15, 2023 | 1212 days past EOL | EOL |
| 1.23 | 1.23.12 | Jul 15, 2022 | Jul 15, 2023 | 1121 days past EOL | EOL |
| 1.24 | 1.24.12 | Oct 19, 2022 | Oct 19, 2023 | 1025 days past EOL | EOL |
| 1.25 | 1.25.11 | Jan 18, 2023 | Jan 18, 2024 | 934 days past EOL | EOL |
| 1.26 | 1.26.8 | Apr 18, 2023 | Apr 18, 2024 | 843 days past EOL | EOL |
| 1.27 | 1.27.7 | Jul 27, 2023 | Jul 27, 2024 | 743 days past EOL | EOL |
| 1.28 | 1.28.7 | Oct 19, 2023 | Oct 19, 2024 | 659 days past EOL | EOL |
| 1.29 | 1.29.12 | Jan 16, 2024 | Jan 16, 2025 | 570 days past EOL | EOL |
| 1.30 | 1.30.11 | Apr 16, 2024 | Apr 16, 2025 | 480 days past EOL | EOL |
| 1.31 | 1.31.10 | Jul 19, 2024 | Jul 19, 2025 | 386 days past EOL | EOL |
| 1.32 | 1.32.13 | Oct 15, 2024 | Oct 15, 2025 | 298 days past EOL | EOL |
| 1.33 | 1.33.14 | Jan 14, 2025 | Jan 14, 2026 | 207 days past EOL | EOL |
| 1.34 | 1.34.14 | Apr 15, 2025 | Apr 15, 2026 | 116 days past EOL | EOL |
| 1.35 | 1.35.13 | Jul 23, 2025 | Jul 23, 2026 | 17 days past EOL | EOL |
| 1.36 | 1.36.9 | Oct 14, 2025 | Oct 14, 2026 | 66 days remaining | Warning |
| 1.37 | 1.37.5 | Jan 13, 2026 | Jan 13, 2027 | 157 days remaining | Warning |
| 1.38 | 1.38.3 | Apr 23, 2026 | Apr 23, 2027 | 257 days remaining | Active |
| 1.39 | 1.39.0 | Jul 14, 2026 | Jul 14, 2027 | 339 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/envoy)
What does Envoy end of life mean for your organization?
When a version of Envoy reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Envoy should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Envoy reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Envoy versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Envoy has 36 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Envoy exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.