ConicPlex

Start Your Project

On this Page

Two Critical NGINX HTTP/2 Flaws Allow Remote Code Execution, Fixed in 1.30.7 and 1.31.9

NGINX fixed two HTTP/2 memory-safety flaws on November 18 that Wiz says can lead to remote code execution. Both need HTTP/2 enabled. Upgrade to 1.30.7 or 1.31.9, or turn HTTP/2 off.

Sajil Memon

November 20, 2026

NGINX fixed two HTTP/2 memory-safety flaws, CVE-2026-123633 and CVE-2026-123007, on November 18 in versions 1.30.7 (stable) and 1.31.9 (mainline). Wiz says either one can lead to remote code execution without authentication, and both only matter when HTTP/2 is enabled. Wiz scores each 9.2 on CVSS 4.0. If you run NGINX with HTTP/2, upgrade now, or switch HTTP/2 off until you can. The sources reviewed report no exploitation in the wild as of November 20.

What the Two Flaws Are

CVE Bug Affected versions Where it bites
CVE-2026-123007 Integer underflow in HTTP/2 flow control, leading to memory corruption 1.9.5 through 1.31.8 Default configurations with HTTP/2 enabled, including servers that only serve static files
CVE-2026-123633 Use-after-free in HTTP/2 connection handling 1.19.7 through 1.31.8 Reverse-proxy setups, when available worker connection slots run low

The flow-control bug is the older and broader one. A refund in ngx_http_v2_filter_cleanup() can push the connection’s send window past its maximum, the bounds check in the window-update handler then underflows, and the result is an out-of-bounds copy. Wiz says it confirmed remote code execution with an ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds, against a server returning ordinary static content over HTTP/2 with TLS on a 64-bit system. It also says attackers can use these bugs to read memory first, so ASLR does not protect you.

The use-after-free is narrower. A connection stays on NGINX’s reusable-connection list while a request is still active, and under connection pressure the GOAWAY error path can free memory the request is still using. The NGINX changelog describes it as a use-after-free in a worker process when worker_connections are not enough.

Severity labels differ by source. Wiz uses CVSS 4.0 9.2 for both. The nginx.org advisories page rates CVE-2026-123007 “major” and CVE-2026-123633 “medium”. Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently found both bugs, according to Wiz. Wiz says it is not releasing its exploits.

Who Is Exposed

Any NGINX build in the ranges above with HTTP/2 turned on. That includes NGINX used as a reverse proxy or load balancer, and plain static-file servers for the flow-control bug. It is NGINX itself that is at fault, so a clean application codebase does not help. Wiz notes that a CDN or WAF terminating HTTP/2 in front of your server may blunt parts of an attack, depending on the implementation, so it is not a substitute for patching.

NGINX Plus is affected too, with separate fixed builds for each CVE. Check F5’s advisories for the exact release numbers instead of assuming the open source version numbers apply.

What To Do Now

  • Find every NGINX instance, including ones baked into container images and ingress controllers, not only the servers you set up by hand.
  • Check which of them have HTTP/2 on: nginx -T 2>/dev/null | grep -n http2 shows it in the running configuration.
  • Upgrade to 1.30.7 or 1.31.9. Some distributions backport fixes without changing the version string, so check your vendor’s advisory before concluding a “1.2x” package is still vulnerable.
  • If you cannot upgrade yet, set http2 off; in the affected server blocks (NGINX 1.25.1 or later) and remove the http2 parameter from any listen directive. Reload, confirm the old worker processes have exited, and test your application, then re-enable HTTP/2 after upgrading.
  • Watch for unexpected worker crashes and commands launched by NGINX worker processes. Wiz calls these general warning signs, not confirmed indicators of compromise.

The Same Release Fixes More Than HTTP/2

According to nginx.org, the 1.31.9 release fixes ten CVEs in total. Wiz lists three more at 9.2 as well: CVE-2026-121810 in HTTP/3, CVE-2026-123634 in the DNS resolver, and CVE-2026-113425 in the mail proxy module. Turning HTTP/2 off does nothing for those. If you use those features, upgrading is the real fix, and if you do not need HTTP/3 or the mail proxy, disabling them reduces exposure in the meantime.

Plenty of WordPress and WooCommerce hosting stacks put NGINX in front of PHP, so this is worth a quick check on any server you manage. We covered another patch that applies to every supported release in PHP’s Security Team Warns of a Critical Release Hitting All Supported Versions. If you want a second pair of eyes on how a WordPress or web application stack is patched and monitored, that is part of our WordPress development and web application development work.

Sources

Sajil Memon is a co-founder of ConicPlex and a Senior Full Stack Developer focused on backend work: Node.js, PHP, APIs, and the infrastructure decisions that determine whether a system holds up under real traffic. He’s spent years on the side of a project that doesn’t get demoed, the part that has to keep working after launch. He writes here about the technical tradeoffs in backend architecture, deployment, and data handling that only become obvious once something breaks in production.

Leave a Reply

Your email address will not be published. Required fields are marked *

Keep reading

Plugins

Illustration of a checkout card with a smaller offer card bumped against it, representing a WooCommerce order bump plugin

How to Add an Order Bump to WooCommerce Checkout without a Funnel Builder (4 Plugins Compared)

Four real plugins that add an order bump to WooCommerce checkout without installing a full funnel builder like CartFlows or…

Sajil Memon

November 20, 2026

News & Updates

PHP’s Security Team Warns of a Critical Release Hitting All Supported Versions

PHP’s security team says a critical release is coming November 19, 2026, for all supported versions. Here is what is…

Sajil Memon

November 19, 2026

Plugins

Illustration of a renewal cycle around a billing card, representing recurring subscription payments in WooCommerce

Free Alternatives to WooCommerce Subscriptions: 4 Real Plugins Compared

WooCommerce has no built-in recurring billing. These 4 real plugins add subscriptions for free or less than the official extension…

Husen Memon

November 19, 2026

WhatsApp
Husen Memon
Husen Memon
Typically replies instant