Envoy Gateway 1.9.1 fixes security issues and changes the upgrade path from 1.9.0

Originally reported November 16, 2026.

Envoy Gateway 1.9.1 restores a 15-second initial fetch timeout for Secret Discovery Service (SDS) and Route Discovery Service (RDS), reversing a change in 1.9.0 that set the timeout to zero. According to the project, waiting indefinitely for a missing Secret or Endpoint could leave clusters in a warming state, block Cluster Discovery Service updates and delay health checks. The restored behavior matches the 1.8.x series.

The upgrade path depends on the version already running. Envoy Gateway recommends that teams on 1.8.x skip 1.9.0 and upgrade directly to 1.9.1. For deployments already on 1.9.0, the project warns that changing SDS configuration during a controller upgrade can affect proxies still running during the rollout. In affected cases, TLS listeners may become active without certificates, causing new handshakes to fail; backend TLS and global rate-limit services may encounter similar certificate or CA problems.

The project recommends a rolling-update configuration to replace proxy Pods quickly, provided the cluster has enough capacity. Replacement can interrupt existing connections, including long-lived WebSocket and gRPC connections. Separately, a production user reported in a GitHub issue that long-running proxies lost their downstream TLS certificates and stopped serving HTTPS until manually restarted. The user linked the incident to changes introduced in 1.9.0; the report is not, by itself, confirmation that every deployment is affected.

The release also addresses security issues. OAuth2/OIDC session-cookie encryption now uses AES-256-GCM, and the legacy AES-256-CBC decryption path has been removed to address the padding-oracle vulnerability identified as CVE-2026-47775. Users with sessions encrypted under the old mechanism will need to authenticate again. Deployments with custom Envoy bootstrap configurations must explicitly set the corresponding runtime configuration.

Other changes add validation for OIDC issuer URLs and fix a security-context issue involving tenant-supplied EnvoyProxy configurations. OCI Wasm image pulls no longer silently fall back from HTTPS to HTTP when a registry rejects HTTPS; HTTP is permitted only when the registry is explicitly configured as insecure. The release also adds per-phase tracing spans for Gateway API and xDS conversion, giving operators more detail when investigating slow processing.

Source: infoq.cn (originally published 2026-11-16 17:06 UTC+8)