# Istio 1.29.8

2026-09-21 · [Original release notes](https://github.com/istio/istio/releases/tag/1.29.8) · [Full summary](https://ratatosk.io/en/releases/istio/1.29.8)

Security 1 · Important fixes 3 · Other changes 1

## Security (1)

### Unsafe kubeconfig handling in `istioctl analyze` fixed

- Affects: `istioctl analyze` setups using multicluster secrets in `istio-system`

Before this release, a crafted secret could make `istioctl` run an exec credential plugin or access local files on the machine running it. The kubeconfigs are now sanitized before Kubernetes clients are built from them.

> - Fixed istioctl analyze building Kubernetes clients directly from istio-system
> multicluster secrets without sanitizing the kubeconfig, which could allow a crafted
> secret to run an exec credential plugin (or read local files via other unsafe auth
> fields) on the machine running istioctl . The kubeconfig is now sanitized the same
> way istiod already sanitizes these secrets.
> Credit : This vulnerability was discovered and reported by Adam Korczynski.
> [Release Notes](https://istio.io/news/releases/1.29.x/announcing-1.29.8/)

https://istio.io/news/releases/1.29.x/announcing-1.29.8/

## Important fixes (3)

### Ambient CNI duplicate redirect rules fixed

- Affects: ambient-mode installations using the CNI node agent’s auto-detected iptables backend

When the CNI node agent restarted, its auto-detected backend could switch from `nft` to `legacy`, causing reconciliation of already-enrolled pods to miss existing rules and add a second redirect ruleset; this behavior is fixed.

> Changes
> - Fixed an issue in ambient mode where the CNI node agent’s auto-detected iptables backend
> ( legacy vs nft ) could flip between agent restarts, causing duplicate
> redirect rules to be written into already-enrolled pods.
> ( Issue #61020 )
> [Release Notes](https://istio.io/news/releases/1.29.x/announcing-1.29.8/)

https://istio.io/news/releases/1.29.x/announcing-1.29.8/

### Random workload gateway selection fixed

- Affects: networks with multiple gateway entries for workload gateway selection

When a network had more than one gateway entry, random selection caused unnecessary WDS pushes on every recompute and could alternate a workload’s gateway address. These effects are fixed.

> [Release Notes](https://istio.io/news/releases/1.29.x/announcing-1.29.8/)
> - Fixed an issue where the network gateway selected for a workload was picked in a random
> order when a network had more than one gateway entry, which caused unnecessary workload
> (WDS) pushes on every recompute and could cause a workload’s gateway address to alternate.

### HTTP/2 restored for JWKS public-key fetches

- Affects: JWKS public-key fetches through HTTP CONNECT proxies

The custom `TLSClientConfig` and `DialContext` disabled automatic HTTP/2, forcing fetches to use HTTP/1.1 and causing them to fail through some of these proxies. Fetches can now use automatically negotiated HTTP/2.

> - Fixed the JWKS resolver forcing all public-key fetches to HTTP/1.1. The custom
> TLSClientConfig and DialContext used for TLS pinning and CIDR blocking caused Go’s
> net/http to disable automatic HTTP/2, so ALPN never negotiated h2. HTTP/2 is now
> re-enabled (matching http.DefaultTransport ), fixing JWKS fetches that fail over HTTP/1.1
> through some HTTP CONNECT proxies.
> ( Issue #61250 )
> [Release Notes](https://istio.io/news/releases/1.29.x/announcing-1.29.8/)

https://istio.io/news/releases/1.29.x/announcing-1.29.8/

## Other changes (1)

- Repeated workload serialization by istiod fixed

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
