News 3 min read

nginx HTTP/2 flaws allow pre-auth RCE: update to 1.30.7 or 1.31.9


nginx 1.30.7 (stable) and 1.31.9 (mainline), released on November 18, 2026, fix two HTTP/2 memory bugs that Wiz Research says let an unauthenticated attacker run code on the server: CVE-2026-123633, a use-after-free, and CVE-2026-123007, an integer underflow in HTTP/2 flow control. Any nginx with HTTP/2 turned on is in scope, and the second bug goes back to nginx 1.9.5 from 2015, so most production servers that speak HTTP/2 need the update. The same release fixes eight more CVEs.

What’s new

In its write-up, Wiz rates both flaws Critical with a CVSS 4.0 score of 9.2. The nginx security advisories page rates them lower: “major” for CVE-2026-123007 and “medium” for CVE-2026-123633.

CVE-2026-123633 CVE-2026-123007
Bug Use-after-free in HTTP/2 Memory corruption in HTTP/2 flow control
Vulnerable (open source) 1.19.7 to 1.31.8 1.9.5 to 1.31.8
Fixed (open source) 1.30.7, 1.31.9 1.30.7, 1.31.9
Fixed (NGINX Plus) 37.0.7.1, 37.2.0.1 37.0.8.1, 37.3.0.1
F5 article K000163928 K000163926

Wiz lists NGINX Plus R33 and 37.0.0 as affected for both.

What an attacker needs, per Wiz:

  • HTTP/2 enabled. No backend app or third-party module is required.
  • CVE-2026-123633 hits reverse-proxy processing when free connection slots run low, so proxy setups are the likelier target.
  • CVE-2026-123007 also works against nginx serving static files. Wiz demonstrated it over HTTPS on 64-bit systems with official 1.31.7 and 1.31.8 builds, by sending a large number of HTTP/2 WINDOW_UPDATE frames.
  • ASLR doesn’t stop it, because the attacker can read memory first.

Wiz says Ikotas Labs, Metnir, Rapid7 and Xint found the flaws independently of it. Wiz reported the first bug to F5 on October 21 and the second on November 16; both went into the November 18 release. Wiz has withheld its proof-of-concept exploits and does not say whether either flaw has been exploited in the wild.

What it means for developers

  1. Check your version with nginx -v. Anything from 1.9.5 up to 1.31.8 with HTTP/2 on is affected.
  2. Upgrade to 1.30.7 or 1.31.9 (or the fixed NGINX Plus builds above), then make sure the distro package or container image you deploy actually contains the fixed version, since those are built separately from the nginx.org release.
  3. If you can’t upgrade today, turn HTTP/2 off. Wiz’s workaround: remove the http2 parameter from every listen directive and, on nginx 1.25.1 or later, also set http2 off; in affected server blocks. On 1.25.1 and later, a leftover listen ... http2 is deprecated but still turns HTTP/2 on. Reload nginx, confirm the old worker processes have exited, test your app over HTTP/1.1, and turn HTTP/2 back on after upgrading.
  4. Know what sits in front of you. A CDN or WAF that terminates HTTP/2 itself may blunt parts of the attack, Wiz says, depending on how it is built. It is not a reason to skip the patch.
  5. Watch for warning signs. Wiz suggests looking into unexpected nginx worker crashes or commands started by the nginx process, and long-lived HTTP/2 connections sending a lot of data for CVE-2026-123007. These are general signals, not confirmed indicators of compromise.

The rest of the release

The same 1.30.7 and 1.31.9 release fixes eight more CVEs, according to nginx.org: use-after-free bugs in the resolver (CVE-2026-123634), HTTP/3 (CVE-2026-121810) and the mail proxy module (CVE-2026-113425); an infinite loop reading request bodies over TLS 1.3 (CVE-2026-118899); a NULL pointer dereference with PROXY protocol v2 (CVE-2026-120993, mainline only); a buffer overflow with alias and try_files (CVE-2026-125283); an SNI bypass in stream client certificate validation (CVE-2026-120967); and weak validation in the stream ssl_preread module (CVE-2026-123640). If you run nginx as a mail proxy, a stream proxy or with HTTP/3, those are more reasons to upgrade now rather than waiting for the next maintenance window.

For another server-side patch that can’t wait this week, see our post on Java4Shell in OpenJDK.

Sources