As reported on November 16, 2026, Envoy Gateway 1.9.1 reverses a discovery-timeout change introduced in 1.9.0, addresses security issues and adds more detailed tracing for gateway configuration processing. The upgrade path depends on which version a deployment currently runs.
Version 1.9.0 set the initial fetch timeout for Secret Discovery Service (SDS) and Route Discovery Service (RDS) to zero. The project found that a cluster waiting indefinitely for a missing Secret or Endpoint could remain in a warming state, blocking Cluster Discovery Service updates and delaying health checks. Version 1.9.1 restores Envoy’s default 15-second timeout, returning to the behavior used in 1.8.x.
Upgrading from 1.9.0 requires particular care. Envoy Gateway warns that changing SDS configuration during a controller upgrade can trigger an Envoy issue affecting proxies still running while the new controller is deployed. In the affected scenario, a TLS listener may become active without a certificate, causing new TLS handshakes to fail. Backend TLS and global rate-limit services may face similar certificate or CA problems. A production user reported on GitHub 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 project recommends that 1.8.x users skip 1.9.0 and upgrade directly to 1.9.1. For existing 1.9.0 deployments, it recommends a rolling-update configuration to replace proxy Pods quickly. That approach requires sufficient cluster capacity and may interrupt existing connections, including long-lived WebSocket and gRPC connections.
On security, 1.9.1 enables AES-256-GCM for OAuth2/OIDC session-cookie encryption and removes the older AES-256-CBC decryption path to address padding-oracle vulnerability CVE-2026-47775. Users with sessions encrypted under the old scheme must authenticate again after the upgrade. Deployments using a custom Envoy bootstrap configuration must explicitly set the relevant runtime option.
The release also adds validation for OIDC issuer URLs and fixes a security-context issue involving tenant-provided EnvoyProxy configurations. OCI Wasm image pulls no longer silently fall back from HTTPS to HTTP when a registry rejects an HTTPS request; HTTP is permitted only when the registry is explicitly configured as insecure.
Other fixes cover namespace-label changes, hostname conflicts, a controller crash when an optional CRD is missing, and incorrect consistent-hashing behavior for UDP routes. Global rate-limit integration now uses Endpoint Discovery Service information for Kubernetes Services and EndpointSlices, while retaining DNS-based behavior when a Service or Endpoint cannot be discovered. New per-phase tracing spans help operators locate delays in Gateway API and xDS conversion.