If you run NGINX with HTTP/2 turned on, you have a patch to install. On November 18, F5 released NGINX open source 1.31.9 and 1.30.7. Together with matching NGINX Plus builds, they fix a set of memory-safety bugs. The worst of these, CVE-2026-123007, has been in the code since NGINX 1.9.5 shipped in September 2015.

The bug is a memory-corruption flaw in how NGINX handles HTTP/2 flow control. Under the right conditions it lets an unauthenticated remote attacker run code inside an NGINX worker process. According to The Hacker News, it has already picked up a nickname: "nginx2root."

Neither F5, Wiz nor Rapid7 has reported any attacks. As of November 18 the flaw was not in CISA's Known Exploited Vulnerabilities (KEV) catalog. However, researchers have already built working exploits in the lab, and Ubuntu and Debian had not shipped fixed packages when The Hacker News published its report. Patch soon. Don't wait to see whether attacks start.

What broke, in plain English

HTTP/2 lets a client and server send many streams of data over one connection. To stop either side from flooding the other, the protocol uses flow control. Each side advertises a "window," which is how much data it is willing to accept, and the other side keeps track of how much of that window is left.

The NVD record, which F5's security team submitted, describes a case where the flow control window can exceed its allowed threshold, potentially causing a heap buffer overflow. The project's own advisory calls the result "memory corruption in HTTP/2 flow control." CyberScoop describes it as an integer underflow: when a client cancels a request while response data is still waiting, NGINX hands back the unused credit without checking whether the total now exceeds the protocol's maximum. A later calculation then wraps into an enormous value, and a memory copy spills outside its buffer. The usual outcome is a crashed worker process (a segfault). Where address space layout randomization (ASLR), a standard memory-protection feature, is disabled or can be bypassed, the overflow can be turned into code execution.

F5 says the bug affects the data plane only, meaning the traffic NGINX serves. It does not touch the control plane.

The exploit is real, but it isn't easy

Reporting from CyberScoop shows both how serious this is and where its limits are. Rapid7's Stephen Fewer built a working exploit against an NGINX 1.31.8 container with HTTP/2 and TLS enabled, but the attack is heavy. It needs about 128 GB of HTTP/2 traffic. The demonstration took two and a half minutes on a fast local network, and CyberScoop puts the transfer at about 17 minutes over a 1 Gbps link. On connections slower than about 300 Mbps, the attack can't finish before NGINX's default one-hour connection limit cuts it off. The exploit also depends on a particular glibc memory-copy routine selected on x86-64 chips with certain AVX-512 features, so not every host is exposed in the same way. Rapid7 said other exploit methods may exist, though none are currently known.

That is some comfort, but not much. The Hacker News reports that Xint's attack worked against its own test servers on AWS, GCP and Azure, and that the firm chained worker-level code execution with a Linux kernel SCTP bug and got root on the host, even with NGINX running inside Docker. Treat the "it only crashes a worker" reading as the best case, not the expected one.

It's not just one bug

CVE-2026-123007 gets the headlines, but it came out alongside several other fixes. The Hacker News reports that F5 scores five of the flaws at 9.2 on CVSS 4.0, which puts them in the critical range, while The Register singles out two of them as the most serious, because they allow unauthenticated remote code execution. The Register describes F5's out-of-band notice as covering ten CVEs in open-source NGINX in total. The nginx.org advisory page lists these entries among them:

  • CVE-2026-123007: HTTP/2 flow-control memory corruption, versions 1.9.5 through 1.31.8.
  • CVE-2026-123633: Use-after-free in HTTP/2, versions 1.19.7 through 1.31.8. The Register says this one is also rated critical at 9.2 and, like CVE-2026-123007, requires HTTP/2 to be enabled.
  • CVE-2026-121810: Use-after-free in HTTP/3, versions 1.25.0 through 1.31.8.
  • CVE-2026-113425: Use-after-free in the mail proxy module.
  • CVE-2026-118899: Infinite loop when reading a request body over TLS 1.3.
  • CVE-2026-123634: Use-after-free in the DNS resolver.
  • CVE-2026-120993: Null-pointer dereference in PROXY protocol v2 handling, versions 1.31.4 through 1.31.8.

A "use-after-free" happens when a program keeps using memory it has already released. This type of bug often leads to crashes and sometimes to code execution. An infinite loop or a null-pointer dereference usually means denial of service: a worker gets stuck or crashes.

Another AI-assisted bug haul

The flaws were reported by several research teams. CyberScoop says F5's advisory credits Rapid7's Stephen Fewer, Wiz Research, Xint.io and Ikotas Labs, and The Register adds Metnir to the list of researchers. Both outlets say AI tools helped find the bugs. According to CyberScoop, Xint's automated harness found four of the five flaws. The Register places NGINX in a recent run of AI-found critical bugs in widely used infrastructure, alongside PHP, Apache and Java.

The potential reach is large. The Register says NGINX runs on about a third of all websites, roughly 225 million. Xint looked at a Shodan snapshot and found that 98.9% of the 11.94 million NGINX hosts whose version it could identify were running an affected release. CyberScoop notes that this figure counts version numbers, not confirmed exposure, because it does not show whether each server accepts HTTP/2 or has received a backported fix. Wiz's Tomer Schwartz told The Register that organizations should treat every internet-connected system as potentially vulnerable.

What It Means for Defenders

Who is affected. Any NGINX open-source build from 1.9.5 through 1.31.8 that serves HTTP/2 is vulnerable to CVE-2026-123007. CVE-2026-123633 covers 1.19.7 through 1.31.8 on HTTP/2 configurations. If you also run HTTP/3, the mail proxy, the resolver or PROXY protocol v2, the other advisories apply too. On the commercial side, the NVD record lists NGINX Plus 37.1.0 before 37.3.0.1 and 37.0.0 before 37.0.8.1 as affected, along with the R33 release line, and The Hacker News says Plus R34 through R36 are affected. F5 did not evaluate versions that are past end of technical support, so assume they are vulnerable. F5 told CyberScoop that BIG-IP and F5OS are not vulnerable and that its cloud services are still being evaluated.

Fixed versions.

  • NGINX open source: 1.31.9 (mainline) or 1.30.7 (stable), or later.
  • NGINX Plus: 37.3.0.1 or 37.0.8.1. The Hacker News reports that no fix was listed for Plus R34 through R36. If you're on one of those, plan a move to a fixed branch.

Distro packages lag behind. When the fixes were published, The Hacker News reported that Ubuntu releases from 16.04 through 26.10 and Debian bookworm, trixie, forky and sid were still listed as vulnerable. A distribution package can carry a fix without changing the version number that nginx -v reports, so compare the full package version with your distribution's own advisory. If you install NGINX from your distribution's repositories, watch its security tracker and apply the update when it ships. If the exposure can't wait, consider temporarily switching to the upstream nginx.org packages.

Do a full restart. The Hacker News notes that reloading the configuration is not enough. A reload leaves the old executable running, and existing connections can stay on old worker processes. You need a full restart or NGINX's binary-upgrade procedure so that the patched code is the code actually running. Afterward, confirm the running version on every host, including containers, sidecars, ingress controllers and appliances that bundle NGINX.

Know where HTTP/2 is enabled. Both critical HTTP/2 bugs require HTTP/2. A server offers it to clients during the TLS handshake by advertising "h2" through ALPN (Application-Layer Protocol Negotiation). Use your scanners or inventory tools to find which internet-facing endpoints advertise h2, and patch those first. Behind a CDN, test the NGINX origin itself. If you can't patch a host right away, disabling HTTP/2 on it blocks CVE-2026-123007 and CVE-2026-123633, according to guidance from CIRCL, the Computer Incident Response Center Luxembourg, cited by The Hacker News. It does not address the HTTP/3, mail proxy or resolver issues.

Harden in depth. Code execution through CVE-2026-123007 depends on ASLR being off or defeated, so check that it hasn't been disabled anywhere. Xint's container-escape chain went through a kernel SCTP bug, so keep host kernels patched, and on hosts that don't use SCTP, block that kernel module from loading, as CIRCL's guidance advises. Treat a container as one layer of protection, not a guarantee. CIRCL suggests watching for NGINX workers that start unexpected programs, workers that exit abnormally or leave core dumps, and long-lived HTTP/2 connections with heavy incoming traffic but few logged requests. A clean access log does not rule out an attack.

For CMMC and federal contractors. Even though this is not in KEV yet, it is an unauthenticated, network-reachable, critical-rated flaw in a common edge component. Record the patch under your flaw-remediation process, and if any affected system can't be patched quickly, document the compensating controls you used, such as disabling HTTP/2.

Sources