Key facts
- No exploitation in the wild had been reported as of disclosure.
- F5 published an advisory on 18 November 2026 addressing five NGINX vulnerabilities.
- The flaws let an unauthenticated remote attacker execute code with NGINX worker-process privileges.
- CVE-2026-123007 is an integer overflow in HTTP/2 flow control causing an out-of-bounds heap write; HTTP/2 on a listening port is the only precondition.
F5 published an advisory Nov. 18, 2026 disclosing five NGINX vulnerabilities that let an unauthenticated remote attacker run code with NGINX worker-process privileges. Rapid7 and F5 disclosed CVE-2026-123007 on Nov. 18, 2026, with Rapid7 calling it a critical integer underflow involving nginx HTTP/2. Rapid7 said the flaw can allow unauthenticated remote code execution when certain conditions hold. OCR: <ocr> Not present </ocr>
The five disclosed flaws carry CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633 and CVE-2026-123634. Wiz, Ikotas Labs, Metnir, Rapid7 and Xint disclosed the flaws independently on Nov. 18, 2026. Xint grouped the five under NGINX2Root, and Ikotas Labs singled out one flaw, NGINX2Shell. OCR: <ocr> Not present </ocr>
For NGINX Open Source, mainline releases from 1.9.5 through 1.31.8 are exposed, and the exposed range differs by flaw. Stable releases in the 1.30.x line, including 1.30.6, are also affected. NGINX Plus versions 37.0.0 through 37.0.7.1 and 37.1.0 through 37.2.0.1 are exposed, along with R34, R35 and R36. Wiz said F5 issued fixes in NGINX Open Source 1.30.7 on the stable line and 1.31.9 on mainline; version 1.31.9 also covers the three flaws from Xint that go beyond the two Wiz reported. OCR: <ocr> Not present </ocr>
CVE-2026-123007 stems from an integer overflow in flow control over HTTP/2, a version of the web protocol, that causes an out-of-bounds heap write. The sole precondition is that HTTP/2 runs on a listening port. CVE-2026-123633 is a use-after-free in upstream connections: it triggers if connection draining closes an active connection over HTTP/2. OCR: <ocr> Not present </ocr>
CVE-2026-121810 is a use-after-free arising during stream creation and on an upstream connection once a QUIC connection — a transport protocol — is drained, and it needs HTTP/3 QUIC with upstream proxy connections like proxy_pass, a routing directive, fastcgi_pass or grpc_pass. CVE-2026-123634 is a use-after-free in DNS resolver waiting-list processing, needing a resolver, a mirror with mirror_request_body off, and proxy_pass built from request data. CVE-2026-113425 is a use-after-free when a client closes a connection during auth_http authentication lookup, needing a mail proxy with proxy enabled and auth_http, an authentication lookup mechanism. OCR: <ocr> Not present </ocr>
NGINX runs on more than 225 million websites worldwide. As of Nov. 10, 2026, Xint found 98.9% of hosts running identifiable nginx versions to be affected. Xint said the most severe flaw permits unauthenticated remote code execution on the most common nginx setup. OCR: <ocr> Not present </ocr>
As of disclosure, no one had reported exploitation in the wild. Xint said it cannot rule out exploitation, since some flaws are old, even though it saw no evidence of in-the-wild use at publication. Worker crashes logged as exited on signal can hint at exploitation attempts, but they are not a reliable sign that code execution succeeded. OCR: <ocr> Not present </ocr>
Rapid7 released a public proof of concept targeting NGINX 1.31.8 packaged as a linux/amd64 Docker image with HTTP/2 and TLS turned on. It consumes roughly 128 GB of HTTP/2 data — two minutes at 10 Gbit/s, 17 at 1 Gbit/s — though a default one-hour connection lifetime in nginx blocks exploitation on networks below roughly 300 Mbit/s. The attack uses a particular x86-64 implementation of glibc memcpy, the C library memory-copy routine, chosen at runtime based on the avx512f and avx512vl CPU features, and Rapid7 says no other way to achieve remote code execution for CVE-2026-123007 is currently known. OCR: <ocr> Not present </ocr>
Wiz confirmed that official NGINX 1.31.7 and 1.31.8 builds allow remote code execution through an ASLR bypass — ASLR is address space layout randomization. Wiz said ASLR and similar memory-safety mitigations offer no protection because attackers can read memory first and execute code later. Wiz also said a single deployment serving several applications can expose multiple services to risk, and that exploitation requires no flaw in the site or application behind NGINX. OCR: <ocr> Not present </ocr>
On Oct. 21, 2026, Wiz reported CVE-2026-123633 to F5, and F5 supplied a patch on Nov. 10, 2026. Wiz reported CVE-2026-123007 to F5 on Nov. 16, 2026, and F5 confirmed it for the Nov. 18 release on Nov. 17, 2026. OCR: <ocr> Not present </ocr>
Xint said every one of the five vulnerabilities carries a proven exploit, even though requirements and the affected versions differ, and that its exploit went from nginx code execution all the way to root on the server, remotely and unauthenticated. Xint said the flaw has existed since nginx added HTTP/2 in 2015. Wiz said CVE-2026-123007 goes back to NGINX 1.9.5 from 2015, spanning more than a decade of exposure, and said the companion use-after-free vulnerability had lasted nearly six years. OCR: <ocr> Not present </ocr>
The company recommends updating to NGINX 1.31.9, and said anyone running without a need for the SCTP kernel module — SCTP is a transport protocol — should block it until a kernel fix exists. It also reported a local-privilege-escalation flaw in the SCTP part of the 4.15 kernel. Xint said chaining that SCTP flaw with the NGINX bug would yield root privileges, though no kernel patch exists yet. OCR: <ocr> Not present </ocr>
CERT-EU rates all five flaws 8.1. Wiz and Xint put them at 9.2 under CVSS 4.0. OCR: <ocr> Not present </ocr>
Several research teams said they used AI models and worked with OpenAI to find the vulnerabilities. Wiz ran its Wiz Atlas AI code-scanning harness and checked impact using Gemini 4 Carbon and ChatGPT 5.6 Sol. Stephen Fewer, a senior principal security researcher at Rapid7, discovered CVE-2026-123007. OCR: <ocr> Not present </ocr>
Brian Pak, co-founder and CEO at Xint, said “disclosure processes established over decades are changing”. F5 asked Xint to limit pre-distribution that could leak, so customers got 24-hour notice of a coming critical update without learning the target. OCR: <ocr> Not present </ocr>
CERT-EU said to apply updates as soon as possible, prioritizing internet-facing appliances. When immediate patching is not possible, turning off HTTP/2 on exposed listeners mitigates CVE-2026-123007 together with CVE-2026-123633. OCR: <ocr> Not present </ocr>

Join the discussion