Envoy 1.40 · Version Status
Envoy 1.40 End of Life Date
Envoy 1.40 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.
✓
Envoy 1.40 is actively supported. EOL date: October 13, 2027.
📅 Get reminded before Envoy 1.40 reaches EOL on October 13, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Oct 13, 2027
362 days remaining
Latest Release
1.40.0
Standard release
Release Date
Oct 13, 2026
Envoy 1.40 series
Lifecycle detail
Envoy 1.40 was released on October 13, 2026 and support is scheduled to end on October 13, 2027 — a planned supported lifespan of 1 year, in line with the 1 year median for Envoy releases. Its most recent patch is 1.40.0, published October 13, 2026.
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 →
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.0 |
Nov 30, 2016 |
EOL |
| 1.1 |
1.1.0 |
Mar 7, 2017 |
EOL |
| 1.2 |
1.2.0 |
May 17, 2017 |
EOL |
| 1.3 |
1.3.0 |
Aug 24, 2017 |
EOL |
| 1.4 |
1.4.0 |
Dec 4, 2017 |
EOL |
| 1.5 |
1.5.0 |
Mar 20, 2018 |
EOL |
| 1.6 |
1.6.0 |
Jun 21, 2018 |
EOL |
| 1.7 |
1.7.1 |
Oct 4, 2018 |
EOL |
What does Envoy 1.40 end of life mean?
When Envoy 1.40 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Envoy 1.40 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Envoy 1.40 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Envoy 1.40 reach end of life?
Envoy 1.40 reaches end of life on October 13, 2027. That is 362 days remaining.
Is Envoy 1.40 still supported?
Yes, Envoy 1.40 is currently supported. The EOL date is October 13, 2027.
What should I upgrade to from Envoy 1.40?
The recommended upgrade from Envoy 1.40 is
Envoy 1.40 — the latest actively supported version. Check the
Envoy full timeline for all supported versions.
What are the security risks of running Envoy 1.40 past EOL?
When Envoy 1.40 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Envoy should migrate immediately or implement compensating controls.