Kyverno End of Life Dates
other
Developers working with Kubernetes security and policy management tools often rely on Kyverno to streamline their workflows and ensure compliance with regulatory requirements. Created to address the complexities of managing Kubernetes environments, Kyverno has been maintained by its community since its inception, providing a robust framework for policy management. The tool's ability to validate and mutate Kubernetes resources has made it an essential component in many development pipelines, allowing developers to focus on writing code rather than managing security configurations.
The Kyverno ecosystem comprises a total of 10 versions, out of which 7 have already reached their end-of-life, leaving 3 active versions that continue to receive support and security updates. The latest stable version, 1.17.2, is the current benchmark for Kyverno deployments, offering the most up-to-date features and security patches. Although there is no next scheduled end-of-life date, the community has been diligent in marking previous versions as unsupported, with the last end-of-life date being 2026-02-02 for version 1.14. This proactive approach to version management ensures that developers can plan their upgrades and migrations well in advance, minimizing potential disruptions to their applications.
From a security perspective, Kyverno has an impressive track record, with a total of 0 known CVEs and 0 critical vulnerabilities. This pristine security posture is a testament to the community's commitment to delivering a secure and reliable product. As a result, there is no most affected version, and no Known Exploited Vulnerabilities (KEV) have been reported. Given this favorable security landscape, developers can confidently continue to use Kyverno in their projects, focusing on leveraging its capabilities to enhance their Kubernetes security and compliance without undue concern for potential vulnerabilities.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.18 | Apr 29, 2026 | — | No | — | 1.18.2 | — | Active | |
| 1.17 | Feb 2, 2026 | — | No | — | 1.17.2 | — | Active | |
| 1.16 | Nov 10, 2025 | — | No | — | 1.16.4 | — | Active | |
| 1.15 | Jul 31, 2025 | — | Apr 29, 2026 | 86d ago | 1.15.20 | — | EOL | |
| 1.14 | Apr 24, 2025 | — | Feb 2, 2026 | 172d ago | 1.14.5 | — | EOL | |
| 1.13 | Oct 29, 2024 | — | Nov 10, 2025 | 256d ago | 1.13.6 | — | EOL | |
| 1.12 | Apr 26, 2024 | — | Jul 31, 2025 | 358d ago | 1.12.7 | — | EOL | |
| 1.11 | Nov 10, 2023 | — | Apr 25, 2025 | 455d ago | 1.11.5 | — | EOL | |
| 1.10 | May 30, 2023 | — | Oct 29, 2024 | 633d ago | 1.10.7 | — | EOL | |
| 1.9 | Feb 1, 2023 | — | Apr 26, 2024 | 819d ago | 1.9.5 | — | EOL | |
| 1.8 | Oct 10, 2022 | — | Nov 10, 2023 | 987d ago | 1.8.5 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
