Security Advisory Desk
unratedQCS priority 76/100Google Cloud

GCP-2026-089

On November 18, 2026, F5 disclosed two serious security issues in various versions of NGINX Open Source and NGINX Plus involving the HTTP/2 protocol. These vulnerabilities can allow unauthenticated remote attackers to crash NGINX worker processes (causing denial of service) or potentially execute code remotely. Google Cloud's core managed services are not affected, but customers running self-managed NGINX on Google Cloud need to upgrade or apply mitigations. Google has temporarily removed affected NGINX images from the Cloud Marketplace while preparing patched versions.

QCS published 21/11/2026, 12:52:20 pm ISTVendor disclosure 21/11/2026, 5:35:07 am ISTVerified 22/11/2026, 2:29:00 am ISTRevision 1

In plain language

What this advisory means

On November 18, 2026, F5 disclosed two serious security issues in various versions of NGINX Open Source and NGINX Plus involving the HTTP/2 protocol. These vulnerabilities can allow unauthenticated remote attackers to crash NGINX worker processes (causing denial of service) or potentially execute code remotely. Google Cloud's core managed services are not affected, but customers running self-managed NGINX on Google Cloud need to upgrade or apply mitigations. Google has temporarily removed affected NGINX images from the Cloud Marketplace while preparing patched versions.

Technical explanation

How the issue affects the environment

Two HTTP/2 vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, affect NGINX Open Source versions 1.9.5 to 1.31.8 and NGINX Plus releases R33+ / 37.x. CVE-2026-123633 is a reentrant HTTP/2 connection-draining heap use-after-free in the ngx_http_v2_module that occurs under conditions of reverse proxying (e.g., with proxy_pass directives) and exhaustion of worker_connections, enabling worker crashes (DoS) or potential remote code execution if Address Space Layout Randomization (ASLR) is disabled or bypassed. CVE-2026-123007 is an HTTP/2 flow-control window vulnerability triggered by crafted HTTP/2 traffic, not requiring reverse proxying, affecting even direct static content serving and allowing worker crashes (DoS) or potential code execution under ASLR disabled/bypassed. Both require specific configurations and traffic to be exploited. Google Cloud's managed load balancing and infrastructure components including Google Front End, Cloud Load Balancing, GKE control plane, Cloud Run, Cloud Functions, and App Engine are unaffected. Customers managing NGINX instances directly on Google Cloud platforms, such as GKE ingress controllers, Compute Engine VMs, or NGINX images from Cloud Marketplace, should upgrade to patched releases (NGINX Open Source 1.31.9 mainline or 1.30.7 stable; NGINX Plus fixed builds 37.0.7.1 / 37.2.0.1 for CVE-123633 and 37.0.8.1 / 37.3.0.1 for CVE-123007) per F5's advisory K000164058. Google has temporarily delisted affected Click-to-Deploy NGINX images from Marketplace until patched versions are ready. Temporary mitigations include disabling HTTP/2 support on exposed NGINX listeners or placing a Google Cloud External Application Load Balancer in front of NGINX translating HTTP/2 to HTTP/1.1, though these mitigations do not address other NGINX vulnerabilities disclosed in the same advisory; upgrading remains recommended.

Operational impact

Why teams should care

Organizations operating their own NGINX servers on Google Cloud may face service disruptions or risk unauthorized remote code execution if attackers exploit these vulnerabilities. This can lead to downtime, data breaches, or compromise of hosted applications. Conversely, users of Google Cloud’s managed services are not affected and do not need to take any action. Mitigation efforts may require operational changes such as patching software or adjusting load balancer configurations, impacting maintenance windows and workloads.

Immediate action

Upgrade all self-managed NGINX Open Source deployments to version 1.31.9 (mainline) or 1.30.7 (stable), and NGINX Plus deployments to the fixed releases listed in F5 advisory K000164058. Monitor F5’s advisory and Google Cloud Marketplace for updated patched images and update accordingly. Apply patches promptly to mitigate all November 18, 2026, F5 NGINX CVEs.

Affected and fixed releases

Affected versionsNGINX Open Source 1.9.5 to 1.31.8, NGINX Plus R33+ / 37.0.0 to 37.3.0.0
Fixed versionsNGINX Open Source 1.31.9 (mainline), NGINX Open Source 1.30.7 (stable), NGINX Plus 37.0.7.1, NGINX Plus 37.2.0.1, NGINX Plus 37.0.8.1, NGINX Plus 37.3.0.1

Temporary risk reduction

If immediate patching is not possible, disable HTTP/2 on all exposed NGINX listeners (e.g., set use-http2: "false" in ingress-nginx controller or remove http2 directives and reload configuration). Alternatively, put a Google Cloud External Application Load Balancer in front of NGINX configured to use HTTP/1.1 for backend communication. Note that these mitigations do not protect against non-HTTP/2 vulnerabilities disclosed in the same advisory.

Evidence and validation checklist

  • F5 master advisory K000164058 disclosing CVE-2026-123633 and CVE-2026-123007
  • Google Cloud Security Bulletin GCP-2026-089 dated November 20, 2026
  • Google Cloud statement excluding managed load balancing and managed infrastructure from impact
  • Guidance to self-managed NGINX users to upgrade or mitigate
  • Temporary delisting of affected NGINX images from Cloud Marketplace by Google

Authoritative reference

Google Cloud Security Bulletins

QCS detected and normalized this record from the official source. Vendor guidance remains authoritative.

Open source