Envoy 1.38 · Version Status
Envoy 1.38 End of Life Date
Envoy 1.38 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Envoy 1.38 is actively supported. EOL date: April 23, 2027.
EOL Date
Apr 23, 2027
349 days remaining
Latest Release
1.38.0
Standard release
Release Date
Apr 23, 2026
Envoy 1.38 series
| 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.38 end of life mean?
When Envoy 1.38 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 Envoy 1.38 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Envoy 1.38 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Envoy 1.38 reach end of life?
Envoy 1.38 reached end of life on April 23, 2027. That is 349 days remaining.
Is Envoy 1.38 still supported?
Yes, Envoy 1.38 is currently supported. The EOL date is April 23, 2027.
What should I upgrade to from Envoy 1.38?
The recommended upgrade from Envoy 1.38 is
Envoy 1.38 — the latest actively supported version. Check the
Envoy full timeline for all supported versions.
What are the security risks of running Envoy 1.38 past EOL?
When Envoy 1.38 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 Envoy should migrate immediately or implement compensating controls.