Istio 1.32 · Version Status

Istio 1.32 End of Life Date

Istio 1.32 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.

✓ Istio 1.32 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
1.32.0
Standard release
Release Date
Nov 9, 2026
Istio 1.32 series
Where these dates come from
ReleaseNov 9, 2026Vendor's own page (our correction) · istio.io · checked Nov 9, 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

Istio 1.32 was released on November 9, 2026 and has no published end-of-life date yet. Its most recent patch is 1.32.0, published November 9, 2026.

← Istio 1.31 All Istio versions
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 Istio Versions
VersionLatestEOL DateStatus
1.7 1.7.8 Feb 25, 2021 EOL
1.8 1.8.6 May 12, 2021 EOL
1.9 1.9.9 Oct 8, 2021 EOL
1.10 1.10.6 Jan 7, 2022 EOL
1.11 1.11.8 Mar 25, 2022 EOL
1.12 1.12.9 Jul 12, 2022 EOL
1.13 1.13.9 Oct 12, 2022 EOL
1.14 1.14.6 Dec 27, 2022 EOL

What does Istio 1.32 end of life mean?

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

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

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