Kubernetes 1.37 · Version Status
Kubernetes 1.37 End of Life Date
Kubernetes 1.37 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Kubernetes 1.37 is actively supported. EOL date: October 28, 2027.
📅 Get reminded before Kubernetes 1.37 reaches EOL on October 28, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Oct 28, 2027
425 days remaining
Latest Release
1.37.0
Standard release
Release Date
Aug 26, 2026
Kubernetes 1.37 series
Lifecycle detail
Kubernetes 1.37 was released on August 26, 2026 and support is scheduled to end on October 28, 2027 — a planned supported lifespan of 1 year and 2 months, in line with the 1 year and 3 months median for Kubernetes releases. Its most recent patch is 1.37.0, published August 26, 2026.
Attack Surface
30/30 Critical 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.16 |
1.16.15 |
Aug 4, 2020 |
EOL |
| 1.17 |
1.17.17 |
Dec 25, 2020 |
EOL |
| 1.18 |
1.18.20 |
Jun 18, 2021 |
EOL |
| 1.19 |
1.19.16 |
Oct 28, 2021 |
EOL |
| 1.20 |
1.20.15 |
Feb 28, 2022 |
EOL |
| 1.21 |
1.21.14 |
Jun 28, 2022 |
EOL |
| 1.22 |
1.22.17 |
Oct 28, 2022 |
EOL |
| 1.23 |
1.23.17 |
Feb 28, 2023 |
EOL |
What does Kubernetes 1.37 end of life mean?
When Kubernetes 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 Kubernetes 1.37 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Kubernetes 1.37 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kubernetes 1.37 reach end of life?
Kubernetes 1.37 reached end of life on October 28, 2027. That is 425 days remaining.
Is Kubernetes 1.37 still supported?
Yes, Kubernetes 1.37 is currently supported. The EOL date is October 28, 2027.
What should I upgrade to from Kubernetes 1.37?
The recommended upgrade from Kubernetes 1.37 is
Kubernetes 1.37 — the latest actively supported version. Check the
Kubernetes full timeline for all supported versions.
What are the security risks of running Kubernetes 1.37 past EOL?
When Kubernetes 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 Kubernetes should migrate immediately or implement compensating controls.
Does Kubernetes track end-of-life by point release (e.g. Kubernetes 1.37.1, Kubernetes 1.37.2)?
No — Kubernetes end-of-life dates apply to the entire 1.37.x release series, not individual point releases. A point release like Kubernetes 1.37.1 or Kubernetes 1.37.2 shares the same EOL date as Kubernetes 1.37. Security patches stop for the entire 1.37.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.