Complete end-of-life dates, support windows, and security status for all Kyverno versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.8 | 1.8.5 | Oct 10, 2022 | Nov 10, 2023 | 911 days past EOL | EOL |
| 1.9 | 1.9.5 | Feb 1, 2023 | Apr 26, 2024 | 743 days past EOL | EOL |
| 1.10 | 1.10.7 | May 30, 2023 | Oct 29, 2024 | 557 days past EOL | EOL |
| 1.11 | 1.11.5 | Nov 10, 2023 | Apr 25, 2025 | 379 days past EOL | EOL |
| 1.12 | 1.12.7 | Apr 26, 2024 | Jul 31, 2025 | 282 days past EOL | EOL |
| 1.13 | 1.13.6 | Oct 29, 2024 | Nov 10, 2025 | 180 days past EOL | EOL |
| 1.14 | 1.14.5 | Apr 24, 2025 | Feb 2, 2026 | 96 days past EOL | EOL |
| 1.15 | 1.15.20 | Jul 31, 2025 | Already EOL | Supported | Active |
| 1.16 | 1.16.4 | Nov 10, 2025 | Already EOL | Supported | Active |
| 1.17 | 1.17.2 | Feb 2, 2026 | Already EOL | Supported | Active |
When a Kyverno version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Kyverno should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →