Kyverno 1.11 · Version Status
Kyverno 1.11 End of Life Date
Kyverno 1.11 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.
⚠
Kyverno 1.11 is past end of life. This version no longer receives security patches. 505 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 25, 2025
505 days past EOL
Latest Release
1.11.5
Standard release
Release Date
Nov 10, 2023
Kyverno 1.11 series
Lifecycle detail
Kyverno 1.11 was released on November 10, 2023 and support ended on April 25, 2025 — a supported lifespan of 1 year and 6 months, longer than the 1 year and 1 month median for Kyverno releases. The last patch it will ever receive is 1.11.5, published May 9, 2024 — 1 year before support ended. It has been without security patches for 1 year and 5 months. 5 newer Kyverno releases have shipped since.
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 →
Extended Support
Extended Kyverno 1.11 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.8 |
1.8.5 |
Nov 10, 2023 |
EOL |
| 1.9 |
1.9.5 |
Apr 26, 2024 |
EOL |
| 1.10 |
1.10.7 |
Oct 29, 2024 |
EOL |
| → 1.11 |
1.11.5 |
Apr 25, 2025 |
EOL |
| 1.12 |
1.12.7 |
Jul 31, 2025 |
EOL |
| 1.13 |
1.13.6 |
Nov 10, 2025 |
EOL |
| 1.14 |
1.14.5 |
Feb 2, 2026 |
EOL |
| 1.15 |
1.15.20 |
Apr 29, 2026 |
EOL |
What does Kyverno 1.11 end of life mean?
When Kyverno 1.11 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 Kyverno 1.11 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Kyverno 1.19 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kyverno 1.11 reach end of life?
Kyverno 1.11 reached end of life on April 25, 2025. This version is no longer receiving security patches.
Is Kyverno 1.11 still supported?
No. Kyverno 1.11 reached end of life on April 25, 2025 and is no longer receiving security patches.
What should I upgrade to from Kyverno 1.11?
The recommended upgrade from Kyverno 1.11 is
Kyverno 1.19 — the latest actively supported version. Check the
Kyverno full timeline for all supported versions.
What are the security risks of running Kyverno 1.11 past EOL?
When Kyverno 1.11 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 Kyverno should migrate immediately or implement compensating controls.