Kiali 2.33 · Version Status
Kiali 2.33 End of Life Date
Kiali 2.33 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.
⚡
Kiali 2.33 reaches end of life on December 31, 2026. Plan your migration now — 81 days remaining.
📅 Get reminded before Kiali 2.33 reaches EOL on December 31, 2026 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Dec 31, 2026
81 days remaining
Latest Release
2.33.0
Standard release
Release Date
Oct 4, 2026
Kiali 2.33 series
Lifecycle detail
Kiali 2.33 was released on October 4, 2026 and support is scheduled to end on December 31, 2026 — a planned supported lifespan of 3 months, shorter than the 7 months median for Kiali releases. It is not an LTS release; Kiali reserves longer patch windows for its LTS versions. Its most recent patch is 2.33.0, published October 4, 2026.
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 Kiali 2.33 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.73 LTS |
1.73.33 |
Supported |
EOL |
| 1.89 |
1.89.8 |
Supported |
EOL |
| 2.0 |
2.0.0 |
Jun 24, 2025 |
EOL |
| 2.1 |
2.1.1 |
Jun 24, 2025 |
EOL |
| 2.2 |
2.2.0 |
Jun 24, 2025 |
EOL |
| 2.3 |
2.3.0 |
Jun 24, 2025 |
EOL |
| 2.4 |
2.4.22 |
Jun 24, 2025 |
EOL |
| 2.5 |
2.5.0 |
Sep 30, 2025 |
EOL |
What does Kiali 2.33 end of life mean?
When Kiali 2.33 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 Kiali 2.33 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kiali 2.33 reach end of life?
Kiali 2.33 reaches end of life on December 31, 2026. That is 81 days remaining.
Is Kiali 2.33 still supported?
Kiali 2.33 is still supported but approaching end of life on December 31, 2026. Begin planning your migration now.
What should I upgrade to from Kiali 2.33?
What are the security risks of running Kiali 2.33 past EOL?
When Kiali 2.33 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 Kiali should migrate immediately or implement compensating controls.