Azure Kubernetes Service 1.37 · Version Status
Azure Kubernetes Service 1.37 End of Life Date
Azure Kubernetes Service 1.37 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.
✓
Azure Kubernetes Service 1.37 is actively supported. EOL date: October 2027.
📅 Get reminded before Azure Kubernetes Service 1.37 reaches EOL in October 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Oct 2027
EOL in October 2027
Latest Release
—
Standard release
Release Date
Oct 2026
Azure Kubernetes Service 1.37 series
Extended Support
Oct 2028
AKS Long Term Support · paid
Where these dates come from
End of lifeOct 2027Vendor's own page (our correction) · learn.microsoft.com · checked Nov 1, 2026medium · 1 source agrees End of extended supportOct 2028Vendor's own page (our correction) · learn.microsoft.com · checked Nov 1, 2026medium · 1 source agrees ReleaseOct 2026Vendor's own page (our correction) · learn.microsoft.com · checked Nov 1, 2026medium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Azure Kubernetes Service 1.37 was released in October 2026 and support is scheduled to end in October 2027 — a planned supported lifespan of 1 year, in line with the 1 year median for Azure Kubernetes Service releases.
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 →
All Azure Kubernetes Service Versions
| Version | Latest | EOL Date | Status |
|---|
| 1.21 |
— |
Jul 31, 2022 |
EOL |
| 1.22 |
— |
Dec 4, 2022 |
EOL |
| 1.23 |
— |
Apr 2, 2023 |
EOL |
| 1.24 |
— |
Jul 31, 2023 |
EOL |
| 1.25 |
— |
Jan 14, 2024 |
EOL |
| 1.26 |
— |
Apr 11, 2024 |
EOL |
| 1.27 |
— |
Jul 31, 2024 |
EOL |
| 1.28 |
— |
Jan 31, 2025 |
EOL |
What does Azure Kubernetes Service 1.37 end of life mean?
When Azure Kubernetes Service 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: 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 Azure Kubernetes Service 1.37 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Azure Kubernetes Service 1.37 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Azure Kubernetes Service 1.37 reach end of life?
Azure Kubernetes Service 1.37 reaches end of life in October 2027. The vendor publishes the month only, not a day.
Is Azure Kubernetes Service 1.37 still supported?
Yes, Azure Kubernetes Service 1.37 is currently supported. The EOL date is October 2027.
What should I upgrade to from Azure Kubernetes Service 1.37?
The recommended upgrade from Azure Kubernetes Service 1.37 is
Azure Kubernetes Service 1.37 — the latest actively supported version. Check the
Azure Kubernetes Service full timeline for all supported versions.
What are the security risks of running Azure Kubernetes Service 1.37 past EOL?
When Azure Kubernetes Service 1.37 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 Azure Kubernetes Service should migrate immediately or implement compensating controls.