GCP-2026-089 — On November 18, 2026, F5 disclosed HTTP/2 vulnerabilities CVE-2026-123633 and CVE-2026-123007 in NGINX Open Source (1.19.7-1.31.8 for…
🔗 CVE IDs covered (2)
📋 Description
Published: 2026-11-20 Description On November 18, 2026, F5 disclosed HTTP/2 vulnerabilities CVE-2026-123633 and CVE-2026-123007 in NGINX Open Source (1.19.7-1.31.8 for CVE-2026-123633; 1.9.5-1.31.8 for CVE-2026-123007) and NGINX Plus, alongside eight additional NGINX CVEs in F5's master advisory (K000164058). Under specific configuration and traffic conditions, an unauthenticated remote attacker can crash an NGINX worker process (DoS) or potentially achieve remote code execution (RCE). Google Cloud's core load balancing and managed infrastructure (including Google Front End, Cloud Load Balancing, GKE control plane, Cloud Run, Cloud Functions, and App Engine) are not affected. This bulletin provides guidance for customers operating self-managed NGINX deployments on Google Cloud. What should I do? Managed Google Cloud services: No customer action is required if you rely solely on unaffected Google Cloud managed platforms (including Google Front End, Cloud Load Balancing, GKE control plane, Cloud Run, Cloud Functions, and App Engine). Google is patching any isolated Google-managed components internally, with zero customer impact and no customer action required. Customer-managed NGINX on Google Cloud (GKE Ingress Controllers, Compute Engine VMs, and NGINX-based Cloud Marketplace images): Google has also temporarily delisted affected Google-maintained Click-to-Deploy NGINX listings on Cloud Marketplace while patched images are being prepared. Patch: Upgrade NGINX Open Source to 1.31.9 (mainline) or 1.30.7 (stable), or NGINX Plus to the latest fixed releases (37.0.7.1 / 37.2.0.1 for CVE-2026-123633; 37.0.8.1 / 37.3.0.1 for CVE-2026-123007) in F5 advisory K000164058 to remediate these vulnerabilities and all November 18 F5 CVEs (see also the Wiz research blog). Temporary mitigation (if unable to patch immediately): Disable HTTP/2 on exposed NGINX listeners (for example, set use-http2: "false" in ingress-nginx or remove http2 listener directives and reload), or place a Google Cloud External Application Load Balancer in front of NGINX configured to speak HTTP/1.1 to backends. (Note: Disabling HTTP/2 does not mitigate non-HTTP/2 CVEs, so upgrading to a patched release remains recommended.) What vulnerabilities are being addressed? CVE-2026-123633 (NGINX Open Source 1.19.7-1.31.8; NGINX Plus R33+ / 37.0.0-37.2.0.0): Reentrant HTTP/2 connection-draining heap use-after-free in ngx_http_v2_module when reverse proxying (proxy_pass, fastcgi_pass, uwsgi_pass, scgi_pass, or grpc_pass) under worker_connections depletion, enabling worker crash (DoS) or potential remote code execution (if ASLR is disabled or bypassed). CVE-2026-123007 (NGINX Open Source 1.9.5-1.31.8; NGINX Plus R33+ / 37.0.0-37.3.0.0): HTTP/2 flow-control window vulnerability during crafted HTTP/2 traffic processing; does not require reverse proxying and can also affect NGINX serving static content directly over HTTP/2, enabling worker process crashes (DoS) or potential remote code execution (if ASLR is disabled or bypassed). Additional F5 November 18, 2026 CVEs: F5 master advisory K000164058 also discloses eight additional NGINX CVEs alongside these two primary HTTP/2 vulnerabilities; upgrading to a patched release remediates these vulnerabilities and all November 18 F5 CVEs. High CVE-2026-123633 CVE-2026-123007