Kiali 2.34 · Version Status

Kiali 2.34 End of Life Date

Kiali 2.34 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.34 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
2.34.1
Standard release
Release Date
Oct 25, 2026
Kiali 2.34 series
Where these dates come from
ReleaseOct 25, 2026Vendor's own page (our correction) · github.com · checked Nov 18, 2026medium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Kiali 2.34 was released on October 25, 2026 and has no published end-of-life date yet. It is not an LTS release; Kiali reserves longer patch windows for its LTS releases. Its most recent patch is 2.34.1, published November 2, 2026.

← Kiali 2.33 All Kiali versions Kiali 2.35 →
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
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 →
All Kiali Versions
VersionLatestEOL DateStatus
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.34 end of life mean?

When Kiali 2.34 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.34 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Kiali 2.35 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Kiali 2.34 reach end of life?
Kiali 2.34 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Kiali 2.34 still supported?
Yes, Kiali 2.34 is currently supported. The EOL date is TBD.
What should I upgrade to from Kiali 2.34?
The recommended upgrade from Kiali 2.34 is Kiali 2.35 — the latest actively supported version. Check the Kiali full timeline for all supported versions.
What are the security risks of running Kiali 2.34 past EOL?
When Kiali 2.34 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.
Deep Dive
Version guide
Kiali EOL: 2.21 to 2.25 Ended With Istio 1.29, October 15, 2026
→
Data from endoflife.date API · Generated at build time · How we source data →