The short version
- The flaws. F5 published fixes on 18 November for five critical NGINX flaws, each able to let an unauthenticated attacker run code on the server. The worst, CVE-2026-123007, is a bug in HTTP/2 handling that has been in the code since 2015.
- Who is affected. Any NGINX release from 1.9.5 to 1.31.8 with HTTP/2 enabled, plus NGINX Plus 37.x before the fixed builds and R34 to R36, for which no fix is listed. Ubuntu and Debian still carried unfixed packages on 18 November.
- Exploitation. Neither F5 nor the researchers have reported attacks in the wild, and CISA's Known Exploited Vulnerabilities catalogue did not list CVE-2026-123007 on 18 November. Proof-of-concept code is on GitHub; Rapid7's method needs about 128 GB of HTTP/2 traffic over a fast link.
- Root access. Code run through the flaws gets the permissions of an NGINX worker process, not root, and F5 says it needs address space layout randomisation to be off or bypassed. Xint reached root on test hosts by chaining a separate Linux kernel SCTP bug, including from inside a container.
- What to do. Move to a fixed release and restart fully rather than reloading. Where that is not possible, turn off HTTP/2, which blocks only two of the five flaws, and apply the separate mitigations for the resolver, HTTP/3 and mail proxy bugs.
Timeline
| Date | Event |
|---|---|
| 22 September 2015 | NGINX 1.9.5 ships, the first release containing CVE-2026-123007. |
| 21 October 2026 | Wiz reports the HTTP/2 use-after-free later tracked as CVE-2026-123633 to F5; F5 says another team had already reported the same bug. |
| 10 November 2026 | F5 gives Wiz a patch for CVE-2026-123633 to review. |
| 16 November 2026 | Wiz reports the second HTTP/2 flaw, later CVE-2026-123007, to F5. |
| 17 November 2026 | F5 confirms the report matches CVE-2026-123007 and will be included in the 18 November release. |
| 18 November 2026 | F5 publishes fixed releases and the five flaws are disclosed publicly. |
What the flaws are
Aikido groups the five under the name nginx2root. The worst, CVE-2026-123007, is an integer underflow in HTTP/2 flow control: NGINX can miscalculate how much response data a client has allowed it to send, and a remote client can cancel queued responses so the server later copies data using an invalid length. That corrupts memory, which Rapid7 says can leak data, interrupt service or execute code.
The other four are memory-safety bugs with their own preconditions: a use-after-free in HTTP/2 connections forwarded to a backend server (CVE-2026-123633), a resolver use-after-free when proxy_pass is built from variables and a subrequest looks up the same name (CVE-2026-123634), the same pattern over HTTP/3 (CVE-2026-121810), and a use-after-free in the mail proxy during auth_http lookups (CVE-2026-113425). F5 rates all five 9.2 under CVSS 4.0.
Code run through the flaws gets the permissions of the NGINX worker process that handles requests, not root. F5 says that requires address space layout randomisation (ASLR) to be off or bypassed; Wiz says it bypassed ASLR in its tests, and Xint says it ran code with nothing more than a reachable HTTP/2 port. Xint reached root on test hosts by chaining a separate use-after-free in the Linux kernel's SCTP transport, a network transport protocol like TCP, even with NGINX inside a Docker container, according to CIRCL and Aikido.
Who is exposed and how hard it is to exploit
Every open-source NGINX release from 1.9.5 through 1.31.8 carries CVE-2026-123007, according to NGINX's advisories. Wiz puts NGINX at more than 225 million websites, and a single deployment often fronts several applications. NGINX Plus is affected in 37.x releases before the fixed builds and in R34 to R36. Distributions shipped versions inside the affected range: Aikido lists Ubuntu 24.04 at 1.24.0 and Debian 12 at 1.22.1, and The Hacker News reported Ubuntu and Debian status pages still listing nginx as vulnerable on 18 November.
CVE-2026-123007 and CVE-2026-123633 need HTTP/2 enabled and reachable. Rapid7's exploit sends roughly 128 GB of HTTP/2 data, taking two and a half minutes in its demonstration, so links slower than about 300 Mbit/s would run past NGINX's default one-hour connection limit and fail. A proxied connection will probably not carry the crafted frames intact, and Rapid7's method depends on a particular memory-copy routine on x86-64 chips with avx512f and avx512vl. Wiz tested official 1.31.7 and 1.31.8 builds; Xint's attack worked on servers at AWS, GCP and Azure, including over a public IP address.
Fixes, mitigations and detection
The fixes are 1.31.9 on mainline and 1.30.7 on stable, with Docker tags for both available on 18 November; F5's advisory covers the NGINX Plus builds and older branches. A reload is not enough: restart fully or use NGINX's live binary upgrade, because existing connections can stay on old workers. Where nginx came from a Linux distribution, compare the full package version with that distribution's advisory, since a backported fix may not change the number nginx -v prints.
Turning off HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633 only. CIRCL gives the steps: on 1.25.1 and later set http2 off and remove it from listen directives, on older releases drop http2 from the listen line, then reload and recheck with openssl s_client -alpn h2. The resolver flaw needs request-time DNS removed from proxy_pass; the mail proxy flaw needs listeners bound to trusted networks or loopback. F5 lists workarounds for only two of the five flaws.
No source reports exploitation in the wild, and CISA's catalogue did not list CVE-2026-123007 as of 18 November. Proof-of-concept code is public on GitHub, but its notes say it only demonstrates the attack against a freshly started Docker container on the same machine. CIRCL suggests watching for workers that start unexpected programs, exit abnormally or leave core dumps, long-lived HTTP/2 connections with heavy inbound traffic but few logged requests, and unusual outbound connections; a clean access log does not rule out an attack.
What is not known yet
- Whether any of the five flaws has been used against a real server; no vendor or researcher has reported an attack, and the absence of a CISA listing on 18 November does not settle it.
- When Ubuntu, Debian and other distributions will publish fixed packages, and which of their releases will receive backports.
- Whether NGINX Plus R34 to R36 will get a fix, and when ingress-nginx users will have a patched option.
- How many internet-facing NGINX deployments accept HTTP/2 on an affected build, including origins hidden behind CDNs.
- When the Linux kernel's SCTP flaw used to gain root will be fixed.
What to do
If you run NGINX
- Check each deployment, including the origin behind a CDN, for HTTP/2: running openssl s_client with -alpn h2 against the server shows ALPN protocol: h2 when it is accepted.
- Update to 1.31.9, with the stable, NGINX Plus and Docker variants named in F5's advisory; if nginx came from your distribution, check the distribution's advisory rather than the version nginx -v prints.
- Restart the service fully or use NGINX's live binary upgrade; a reload leaves the old executable serving existing connections.
- If you cannot update yet, turn off HTTP/2 and HTTP/3, remove request-time DNS from proxy_pass, and restrict mail proxy listeners, because disabling HTTP/2 alone does not cover the resolver or mail proxy flaws.
If you run ingress-nginx
- Turn off HTTP/2: CVE-2026-123633 applies to ingress-nginx and no patch is planned for it.
- Plan a move to a maintained ingress controller or to an NGINX build on a fixed release.
If you manage Linux hosts
- Block the SCTP module where it is not needed by adding install sctp /bin/false to a file under /etc/modprobe.d; this does not unload a module already loaded or disable SCTP built into the kernel.
- Look for NGINX workers that start unexpected programs, exit abnormally or leave core dumps, and for long-lived HTTP/2 connections carrying heavy inbound traffic with few logged requests.
Update log
- First published.
Sources
- 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers
- nginx2root: Critical nginx RCE vulnerabilities [CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425]
- Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007
- CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.