2026-11-19 - NGINX HTTP/2 vulnerabilities (CVE-2026-123633 and CVE-2026-123007)¶
Last updated: 2026-11-19
Are Wire installations affected?¶
Kubernetes ingress-nginx is affected when it runs an unpatched NGINX build with HTTP/2 enabled. This applies to Wire installations that use the affected ingress-nginx controller, including the controller bundled with ingress-nginx Helm chart 4.11.5. The vulnerabilities can allow unauthenticated remote code execution in the NGINX worker process. See the NGINX security advisories.
Recommended ingress-nginx image override¶
Wire recommends overriding the controller image with the digest-pinned, multi-architecture build below. It is available for Linux AMD64 and ARM64.
Chainguard's ingress-nginx controller v1.15.16 includes backports of the NGINX 1.30.7 fixes for CVE-2026-123633 and CVE-2026-123007 to its bundled NGINX 1.27.1. The patched binary still reports nginx/1.27.1. Both HTTP/2 patches were added in v1.15.15 and carried forward into v1.15.16. The v1.15.16 release diff linked from the release notes shows the additional security backports. Chainguard fork release notes · v1.15.16 release diff · Diff adding both HTTP/2 patches
Merge these values into your existing wire/ingress-nginx-controller release values, then upgrade the release. For a standalone upstream ingress-nginx chart, place controller at the top level.
If you collect ingress metrics, keep both metrics settings shown above. Chart 4.11.5 creates the metrics Service with controller.metrics.enabled, but the patched controller also needs --enable-metrics=true to export nginx_ingress_controller_* metrics. After the rollout, verify those metrics are available at the controller's /metrics endpoint.
NGINX license and copyright notice¶
The following license accompanies the NGINX 1.27.1 binary bundled in the Wire controller image. NGINX 1.27.1 source archive