Envoy 1.37 · Version Status

Envoy 1.37 End of Life Date

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

Envoy 1.37 reaches end of life on January 13, 2027. Plan your migration now — 178 days remaining.
📅 Get reminded before Envoy 1.37 reaches EOL on January 13, 2027 — alerts 90, 30 & 7 days out.
Google →
EOL Date
Jan 13, 2027
178 days remaining
Latest Release
1.37.5
Standard release
Release Date
Jan 13, 2026
Envoy 1.37 series
← Envoy 1.36 All Envoy versions Envoy 1.38 →
18 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
8/40
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 →
Recommended upgrade path
Envoy 1.38
Latest release: 1.38.3 · EOL: Apr 23, 2027
View full Envoy timeline →
Extended Support
Extended Envoy 1.37 support is available

Commercial vendors offer security patches beyond EOL — compare your options.

Compare Options →
All Envoy Versions
VersionLatestEOL DateStatus
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.37 end of life mean?

When Envoy 1.37 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.37 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.37 reach end of life?
Envoy 1.37 reached end of life on January 13, 2027. That is 178 days remaining.
Is Envoy 1.37 still supported?
Envoy 1.37 is still supported but approaching end of life on January 13, 2027. Begin planning your migration now.
What should I upgrade to from Envoy 1.37?
The recommended upgrade from Envoy 1.37 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.37 past EOL?
When Envoy 1.37 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.
Data from endoflife.date API · Generated at build time · How we source data →