Nginx HTTP/2 Vulnerability: Remote Code Execution Fixed in 1.30.7

The nginx HTTP/2 vulnerability CVE-2026-123633 and CVE-2026-123007 allow remote unauthenticated code execution. Patch to nginx 1.30.7 or 1.31.9.

Threat AdvisoryLast updated

What Happened

On November 18, 2026, nginx released fixes for two flaws in its HTTP/2 implementation, CVE-2026-123633 and CVE-2026-123007. Together the nginx HTTP/2 vulnerability pair lets a remote, unauthenticated attacker run code on an nginx server that accepts HTTP/2 connections, per Google Cloud bulletin GCP-2026-087. Cisco PSIRT gives the issue a Security Impact Rating of Critical, and Google Cloud rates its bulletin Critical.

For an MSP, the awkward part is where nginx usually sits. It is rarely the product you sell. It is the reverse proxy, ingress controller, load balancer or marketplace image in front of a client's application, and often a build nobody has inventoried since it was deployed. The affected range, nginx releases 1.9.5 through 1.31.8 per Cisco PSIRT, is wide enough to cover builds shipped years apart. Code execution on that host means the client's application is the one that goes down, and you are the one paged.

AWS says it is actively deploying mitigations worldwide, and that WAF managed and custom rules cannot effectively detect or block these issues because they can be leveraged at the HTTP/2 protocol layer before a complete HTTP request is formed.

Timeline

  • Wed, 18 Nov 2026: Sophos PSIRT first publishes advisory sophos-sa-20261118-nginx2root, covering CVE-2026-123007 and CVE-2026-123633 alongside other NGINX CVEs.
  • November 18, 2026: nginx announces the availability of a fix for multiple critical vulnerabilities that could lead to remote code execution, according to Cisco PSIRT.
  • November 19, 2026: Ubuntu Security publishes USN-9159-1 for the nginx vulnerabilities.
  • November 19, 2026: Google Cloud publishes bulletin GCP-2026-087, rating CVE-2026-123633 and CVE-2026-123007 Critical.
  • 11/19/2026 15:00 PM PST: AWS publishes bulletin 2026-192-AWS.
  • November 20, 2026: Google Cloud publishes GCP-2026-089 with patch guidance and the temporary mitigation for customers running self-managed NGINX.
  • November 20, 2026: Cisco PSIRT publishes its advisory on the vulnerabilities affecting Cisco products.
  • Fri, 20 Nov 2026: Sophos PSIRT updates its advisory to Article Version 3.

Who Is Affected

Any host running an nginx version in the affected range with HTTP/2 accepted on a listener that is reachable from an untrusted network. The affected list published by the sources:

For an MSP the risk is not the number of affected versions, it is the number of clients behind them. If a shared proxy serves many clients, one host is the blast radius. If the nginx instance sits inside a client's site, the site is the blast radius and the rebuild is yours to run.

  • nginx releases 1.9.5 through 1.31.8, fixed in 1.31.9 (mainline) and 1.30.7 (stable).
  • Ubuntu installations: Ubuntu Security states CVE-2026-123007 and CVE-2026-123633 affected Ubuntu 16.04 LTS, 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS, 26.04 LTS and 26.10.
  • Customer-managed NGINX on Google Cloud, including GKE Ingress Controllers, Compute Engine VMs and NGINX-based Cloud Marketplace images, per Google Cloud bulletin GCP-2026-089.
  • The Router in Apigee Edge for Private Cloud 4.54.00 and 4.53.01 uses an nginx version in the affected range, but Google Cloud states Routers are not affected in the default and supported configuration because HTTP/2 is not supported on Router virtual hosts.

Technical Details: The Nginx HTTP/2 Vulnerability

CVE-2026-123633. Cisco PSIRT identifies it as an NGINX ngx_http_v2_module vulnerability. Ubuntu Security states nginx did not correctly handle certain reusable HTTP/2 connections, and that a remote attacker could possibly use this issue to cause a denial of service or execute arbitrary code. Google Cloud lists 1.19.7 through 1.31.8 as the affected range for this CVE.

CVE-2026-123007. Cisco PSIRT identifies it as an NGINX ngx_http_v2_module vulnerability. Ubuntu Security states nginx did not correctly handle certain memory operations, and that a remote attacker could possibly use this issue to cause a denial of service or execute arbitrary code. Google Cloud lists 1.9.5 through 1.31.8 as the affected range for this CVE.

Attack vector. Google Cloud states an unauthenticated remote attacker can target an nginx server that accepts HTTP/2 connections, and that under specific configuration and traffic conditions the attacker can crash an NGINX worker process (DoS) or potentially achieve remote code execution (RCE).

Fixed versions. nginx 1.31.9 (mainline) and 1.30.7 (stable), per Google Cloud's GCP-2026-089 and Cisco PSIRT's advisory. Google Cloud also lists NGINX Plus fixed releases: 37.0.7.1 and 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 and 37.3.0.1 for CVE-2026-123007, in F5 advisory K000164058. Google Cloud states no customer action is required for its managed platforms, including Google Front End, Cloud Load Balancing, GKE control plane, Cloud Run, Cloud Functions and App Engine.

Cisco PSIRT's advisory also lists CVE-2026-113425, CVE-2026-121810 and CVE-2026-123634 in the same November batch. No source states that either of the two HTTP/2 flaws has been exploited in the wild.

Why Edge Filtering Does Not Cover This

AWS states plainly that WAF managed and custom rules cannot effectively detect or block these issues. The reason it gives: they can be leveraged at the HTTP/2 protocol layer before a complete HTTP request is formed, so a rule that inspects requests never sees the attack.

As a general rule, protocol layer bugs sit below the tools most MSPs lean on. Edge filtering, rate limiting and request inspection all assume there is a request to inspect. When the flaw fires earlier than that, the server itself is the only control point. Plan for that class of bug by patching the server and keeping the exposed HTTP/2 surface as small as the application allows.

What MSPs Should Do

Patching is the fix. Google Cloud's guidance is to upgrade, with disabling HTTP/2 as the temporary mitigation if you cannot patch immediately.

  1. Find every nginx instance you manage. Reverse proxies, ingress controllers, load balancers, appliances, marketplace images, containers, and client-owned hosts you patch. Check both mainline and stable builds.
  2. Upgrade NGINX Open Source to 1.31.9 (mainline) or 1.30.7 (stable), per Cisco PSIRT and Google Cloud.
  3. Upgrade NGINX Plus to the listed fixed releases: 37.0.7.1 or 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 or 37.3.0.1 for CVE-2026-123007, per Google Cloud citing F5 advisory K000164058.
  4. Patch Ubuntu hosts through the distribution. Ubuntu Security published USN-9159-1 on November 19, 2026.
  5. If you cannot patch immediately, disable HTTP/2 on exposed NGINX listeners, as Google Cloud advises. Treat it as a stopgap, not a fix.
  6. Check the cloud platform before assuming you need to act. Google Cloud states its managed platforms are not affected and that it is patching isolated Google-managed components internally.
  7. Confirm the fix on the running service, not just in the package manager. Reload or restart nginx and verify the version the service reports.
  8. Record which clients were exposed and when the upgrade landed. You will want that list if a client asks.
  9. As a standing practice, keep an inventory of web and proxy software with versions and owners, and treat out-of-band patch releases as scheduled work rather than best effort.

How EnterProtect Helps

EnterProtect backup keeps clean, restorable copies of the systems your clients run on. When an internet facing host has to be rebuilt, the difference between one bad day and one lost week is whether you hold a recent copy you trust.

Recovery gets a client running again after an outage or a rebuild, so restoring service does not wait on someone reassembling a server by hand.

Vulnerability scanning keeps a current view of the software versions exposed across the environments you manage, so a wide affected range becomes a work list instead of a guess about what to patch first.

Frequently Asked Questions

What Is CVE-2026-123633?

CVE-2026-123633 is one of two nginx HTTP/2 module vulnerabilities announced on November 18, 2026. Cisco PSIRT identifies it as an NGINX ngx_http_v2_module vulnerability, and Ubuntu Security states nginx did not correctly handle certain reusable HTTP/2 connections. A remote attacker could possibly use the issue to cause a denial of service or execute arbitrary code.

Which Nginx Versions Are Affected by CVE-2026-123007 and CVE-2026-123633?

nginx releases 1.9.5 through 1.31.8 fall in the affected range, and the flaws are fixed in 1.31.9 (mainline) and 1.30.7 (stable). Google Cloud lists the affected range for CVE-2026-123633 as 1.19.7 through 1.31.8, and for CVE-2026-123007 as 1.9.5 through 1.31.8. NGINX Plus is affected too, with fixed releases listed by Google Cloud from F5 advisory K000164058.

Is Disabling HTTP/2 Enough to Fix This?

Google Cloud lists disabling HTTP/2 on exposed NGINX listeners as a temporary mitigation if you cannot patch immediately. It is not the fix. The remediation is upgrading to 1.31.9 (mainline) or 1.30.7 (stable), or to the fixed NGINX Plus releases.

Do I Need to Act If My Nginx Runs on Google Cloud Managed Services?

Google Cloud states its managed platforms, including Google Front End, Cloud Load Balancing, GKE control plane, Cloud Run, Cloud Functions and App Engine, are not affected, and that no customer action is required for them. Customer-managed NGINX on Google Cloud, such as GKE Ingress Controllers, Compute Engine VMs and NGINX-based Cloud Marketplace images, still needs patching. Google also states it temporarily delisted affected Click-to-Deploy NGINX listings on Cloud Marketplace while patched images were prepared.

Can a Web Application Firewall Block These Nginx HTTP/2 Attacks?

AWS states that its WAF managed and custom rules cannot effectively detect or block these issues, because they can be leveraged at the HTTP/2 protocol layer before a complete HTTP request is formed. That is a reason not to treat WAF coverage as a substitute for patching. Plan the upgrade instead.

Has Either Flaw Been Exploited in the Wild?

None of the sources for this advisory report exploitation of CVE-2026-123633 or CVE-2026-123007 in the wild. Treat that as a reason to patch on your normal schedule rather than a reason to skip it, especially with fixed versions already published.

Sources

  • Advisory: NGINX Vulnerabilities - nginx2root (CVE-2026-123007 and others) (Sophos Psirt Feed)
  • USN-9159-1: nginx vulnerabilities (Ubuntu Security)
  • Issue with nginx HTTP/2 Implementation (Aws Bulletins)
  • Vulnerabilities in nginx Affecting Cisco Products: November 2026 (Cisco Psirt)
  • GCP-2026-087 (Google Cloud Security Corrected)
  • GCP-2026-089 (Google Cloud Security Corrected)

Check Your Clients' External Exposure

EnterProtect Vulnerability Scanning checks your clients' domains, addresses and exposed services. A critical CVE pages you like any critical alert, with the fix named.

Join the WaitlistJoin before it launches to get the Founding Partner Rate.

More Threat Advisories

See All Threat Advisories

Priya Nair

Partner Specialist

Priya Nair said: Hi, I'm Priya, EnterProtect's AI partner specialist. Ask me what a product does, what it costs, or what you'd keep per client.

Priya · Just now

Privacy