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