A neon server-room illustration shows an NGINX reverse proxy handling HTTP/2 and HTTP/3 traffic with a security update.
Two of the five NGINX flaws grabbing headlines this week, CVE-2026-123007 and CVE-2026-123633, can let an unauthenticated attacker execute code on an NGINX web server. If you run NGINX as a reverse proxy, an ingress layer in front of Windows-hosted apps, or inside a container, this one goes on today's patch list. The flaws are dubbed "NGINX2Root", but the name oversells what each bug does alone, and the exposure numbers need careful reading.

A neon server-room illustration shows an NGINX reverse proxy handling HTTP/2 and HTTP/3 traffic with a security update. What was disclosed​

F5 publicly disclosed several memory corruption vulnerabilities in NGINX Open Source and NGINX Plus on November 18, 2026. The "NGINX2Root" label comes from Xint's research, and it covers five CVEs:

  • CVE-2026-123007: HTTP/2 flow-control memory corruption. nginx.org rates it "major" and lists it as affecting versions 1.9.5 through 1.31.8.
  • CVE-2026-123633: an HTTP/2 use-after-free affecting 1.19.7 through 1.31.8. It matters when NGINX accepts HTTP/2 and proxies requests to a backend.
  • CVE-2026-121810: an HTTP/3 (QUIC) use-after-free affecting 1.25.0 through 1.31.8.
  • CVE-2026-123634: a resolver use-after-free affecting 0.6.18 through 1.31.8.
  • CVE-2026-113425: a mail-proxy use-after-free affecting 0.5.33 through 1.31.8. nginx.org rates it "major".

BleepingComputer reports that the two HTTP/2 bugs were found independently by researchers at Xint, Wiz, Ikotas Labs, Metnir and Rapid7. Xint also found the other three.

Severity scores​

F5 scores all five at 9.2 under CVSS v4.0 and 8.1 under CVSS v3.1. The nginx.org project uses its own scale. It rates CVE-2026-123007 and CVE-2026-113425 as major and the other three as medium. This is why you will see "critical" in some headlines and "medium" in others. The two systems are scoring different things.

"Root" needs a caveat​

The name implies each bug hands over the whole machine. They don't.

  • F5 says the typical result is a crash of the nginx worker, the process that handles live traffic. Code execution is possible where ASLR (memory-address randomization) is disabled or bypassed.
  • Code execution through NGINX happens in the worker's security context.
  • The root claim comes from a chain. BleepingComputer reports that Xint demonstrated root access by combining an NGINX flaw with a separate Linux kernel bug in the SCTP subsystem. That chain was used to escape an NGINX Docker container and reach root on the host.
  • Xint identified a separate, unpatched Linux kernel SCTP use-after-free with no CVE assigned as of November 18. Patching NGINX removes the entry point, but the kernel bug remains until distributions ship fixes.

Wiz demonstrated unauthenticated remote code execution against a server hosting ordinary static files over HTTP/2 with TLS. It also demonstrated code execution for CVE-2026-123633, but is not releasing those proofs of concept. Not everyone agrees on how public the exploit code is. Tenable says a public PoC exists for CVE-2026-123007. Red Hat's bulletin also says a proof of concept is publicly available.

Censys reproduced the underlying memory corruption in four of the five flaws in lab testing but did not achieve remote code execution. Reproducing a crash confirms a bug. It does not prove a working exploit.

Is anyone exploiting this?​

F5, Wiz and Rapid7 reported no known attacks exploiting the flaw. That was the state at disclosure, and it can change quickly when a public PoC exists, so treat it as a snapshot rather than a guarantee.

Who is actually exposed​

The headline scan numbers are alarming, but they are weak evidence of real exposure.

  • Xint reported that 98.9% of NGINX hosts disclosing a recognizable version fall in the affected range. That figure ignores whether HTTP/2 is on and whether the fix was backported.
  • Censys estimates about 8.8 million NGINX services were potentially exposed to CVE-2026-123007 as of November 19, based on version and HTTP/2 support. It says more than 511,000 previously exposed services have since been patched or mitigated. Another 104 million NGINX services don't disclose a version.
  • Researcher Florian Roth called the issue worse than Node2Shell and Java2Shell but not an imminent threat for most deployments. He noted the flaws are exploitable in non-default configurations and called version-only exposure claims misleading. In a sample of a few hundred Shodan HTTPS endpoints, he found roughly 66% supported HTTP/2. That is a small sample, not a measure of all NGINX deployments.

The practical reading: the number of truly exploitable servers is much smaller than 8.8 million, but nobody can state it precisely. Banners are an unreliable guide in both directions.

Conditions for each flaw​

Red Hat's bulletin gives the clearest condition list:

  1. CVE-2026-123007: NGINX acting as a web server or proxy with HTTP/2 enabled on a listen directive.
  2. CVE-2026-123633: NGINX acting as an HTTP/2 reverse proxy to a backend.
  3. CVE-2026-121810: QUIC/HTTP/3 enabled.
  4. CVE-2026-123634: an HTTP proxy with a resolver directive for dynamic server names, combined with SSI or the mirror directive.
  5. CVE-2026-113425: a mail proxy with a mail {} block.

Red Hat says a deployment serving only static files, with no HTTP/2, HTTP/3, mail proxy or dynamic proxy resolution, is not affected by these five. HTTP/2 is common, so for most internet-facing sites that exemption won't apply to CVE-2026-123007.

How to fix it​

Patch. NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline) fix the flaws. NGINX Plus users should move to 37.0.8.1 or 37.3.0.1. After updating, restart NGINX so the patched binary loads.

A few caveats from the wider coverage:

  • SOCRadar reports that NGINX Plus R33 through R36 have no patch, so those customers must move to a 37.x build. Precursor Security, citing F5's advisory, lists R34 to R36 as vulnerable with no fixed release. Confirm your exact build against F5's advisory K000163926.
  • Linux distributions may backport fixes without changing the reported NGINX version, so check your distribution's security advisories. A scanner reading the banner can flag a patched box or miss an unpatched one.
  • GetPageSpeed reports that OpenResty, Angie, Tengine and freenginx are built on the affected code, and none had published a fix or statement by November 19. That is a third-party observation. Check each project directly if you use one.
  • Containers and appliances that bundle NGINX need rebuilding or vendor updates. Red Hat notes that containers based on RHEL or UBI images should be rebuilt once the base images update.

Mitigate if you can't patch yet. Match the workaround to the flaw. Disabling HTTP/2 only covers two of the five.

FlawTemporary mitigation
CVE-2026-123007, CVE-2026-123633Disable HTTP/2: remove the http2 parameter from listen directives and, on nginx 1.25 and later, set http2 off;
CVE-2026-121810Remove the quic parameter from listen directives and set http3 off;
CVE-2026-123634Disable proxy configurations that combine dynamic backend lookup with SSI or mirror
CVE-2026-113425Remove mail proxying, or restrict mail ports to trusted clients (partial mitigation)

Xint notes that disabling HTTP/2 does not protect against CVE-2026-123634, CVE-2026-121810 or CVE-2026-113425, so it is not advised as a blanket workaround. Red Hat also warns that disabling HTTP/2 can hurt performance for clients that rely on multiplexing.

A quick triage routine​

  1. Inventory every NGINX instance, including reverse proxies, ingress controllers, appliances and container images.
  2. Prioritize internet-facing listeners that accept HTTP/2.
  3. Check configuration, not just version: HTTP/2 or HTTP/3 listeners, resolver with mirror or SSI, and any mail {} block.
  4. Verify the patch through your distribution's advisory or the package changelog, rather than the banner alone.
  5. Apply mitigations only as a bridge, then retest the service.
  6. Watch kernel updates for the SCTP fix if you run containerized NGINX, since the container-escape chain depends on it.

Not just the five​

The same release fixes other NGINX bugs. BleepingComputer highlights CVE-2026-118899, which nginx.org lists as "major". An unauthenticated attacker can send a worker into an infinite loop while it reads a request body over TLS 1.3, causing denial of service. Because the patch covers it, upgrading rather than mitigating bug by bug is the efficient route.

The takeaway​

This is a real, patchable, serious set of bugs, and a public PoC reportedly exists for the main one. It is not a "every NGINX server on earth is owned" event. For Windows-centric shops, the NGINX box you forgot about, such as the ingress in front of an app tier or the proxy inside a vendor appliance, is the one most likely to be missed. Check those first, and don't trust a version banner to tell you whether you're safe.

 

References

  1. RHSB-2026-019 Heap overflow - nginx HTTP/2 (CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425) - "NGINX2Root" | Red Hat Customer Portal access.redhat.com
  2. Critical NGINX ‘NGINX2Root’ bugs let attackers hijack servers BleepingComputer 2026-11-19T09:57:24-05:00
  3. NGINX2Root FAQ: Five vulnerabilities in NGINX (CVE-2026-123007) tenable.com