READ. SCROLL. LISTEN.

Unbiased headlines. Facts, not spin.

Unbiased Headlines is an independently owned news organization. We bring you the facts, not opinions, written fresh from 110+ named sources. Sources linked so you can verify it yourself.

← Back to headlines

F5 Fixes Five Critical NGINX Remote Code Execution Flaws; Public Exploit Exists, No Attacks Reported

F5 Fixes Five Critical NGINX Remote Code Execution Flaws; Public Exploit Exists, No Attacks Reported
F5 shipped an out-of-band release on Nov. 18 fixing five NGINX flaws, each rated 9.2 on CVSS 4.0, that can let an unauthenticated attacker run code as an NGINX worker. A public exploit exists for the HTTP/2 bug, which dates to 2015, and no exploitation in the wild has been reported. Patching depends on distribution packages and a full restart, and the Linux kernel flaw Xint chained with it still has no fix.

F5, the company behind NGINX, shipped an out-of-band security release on Wednesday, Nov. 18, 2026, fixing five flaws that can let an unauthenticated remote attacker run code with the privileges of an NGINX worker process. The CVEs are CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. F5 scores all five 9.2 out of 10 on CVSS 4.0.

No one has reported attacks. F5 makes no mention of exploitation in the wild, Wiz and Rapid7 have reported none, and CISA's Known Exploited Vulnerabilities catalog did not list the flaws as of Nov. 18.

What was fixed

The fixed versions are NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable), which cover all five flaws. NGINX Plus is fixed in 37.3.0.1 and 37.0.8.1. The Hacker News reports that F5 lists no fixed release for NGINX Plus R34 through R36.

The release fixed ten NGINX vulnerabilities in total, Tenable reported. The nginx.org advisory page rates CVE-2026-123007 "major" and CVE-2026-123633 "medium," a different scale from F5's CVSS score.

The security firm Xint found all five flaws and grouped them under the name "nginx2root." F5 and nginx.org do not use that name, according to Tenable. Xint told F5 about the bugs through HackerOne on Oct. 16, Tenable reported. Wiz, Ikotas Labs, Metnir and Rapid7 independently reported the two HTTP/2 flaws.

Which servers are exposed

The most widely reachable flaw is CVE-2026-123007, an HTTP/2 flow-control bug that needs only HTTP/2 to be switched on. It has been in every NGINX release from 1.9.5, which added HTTP/2 in September 2015, through 1.31.8. That includes the releases from Oct. 14 and Oct. 21.

The other four each need a specific setup, according to Xint:

  • CVE-2026-123633: HTTP/2 with requests forwarded to a backend server.
  • CVE-2026-123634: a resolver flaw that needs a proxied server name built from request variables, plus a subrequest created by SSI or the mirror directive.
  • CVE-2026-121810: HTTP/3 with requests forwarded to a backend server.
  • CVE-2026-113425: NGINX used as a mail proxy.

Wiz says it achieved code execution against NGINX serving only static files, with no backend application and no third-party modules.

Censys estimates about 9 million NGINX services run an affected version with HTTP/2 on. Not every one of those is necessarily reachable. A server behind a CDN that accepts only HTTP/1.1 at the origin cannot be attacked over HTTP/2.

How easy is exploitation?

F5's position is narrower than the 9.2 score might suggest. It says code execution is possible only where address space layout randomization (ASLR) is disabled or can be bypassed.

Wiz and Rapid7 say ASLR is no barrier. Wiz says it bypassed ASLR in tests. Rapid7's public exploit, written by researcher Stephen Fewer, defeats it by leaking memory addresses, according to SecurityWeek.

Rapid7 also lists practical limits. Its exploit needs roughly 128 GB of HTTP/2 traffic, most of it control frames. That took two and a half minutes on a fast local network, about two minutes over a 10 Gbit/s link and seventeen minutes over 1 Gbit/s. NGINX closes connections after an hour by default, so Rapid7 says a link slower than about 300 Mbit/s cannot finish in time.

The exploit also relies on a specific x86-64 glibc memory-copy routine, chosen at runtime on CPUs with certain AVX-512 features. Rapid7 says other exploitation methods may exist but none are known. If an HTTP/2 connection is proxied, the attacker's frames will likely not be retransmitted in a form that works.

Censys says it reproduced the bug's behavior over cleartext HTTP/2 without that traffic volume, SecurityWeek reported. A proof-of-concept is on GitHub. Its notes say it is suitable only for demonstrating the attack against a freshly started Docker container on the same machine.

The kernel chain

Code running as an NGINX worker is not root. Xint says it also found a separate Linux kernel flaw in the SCTP subsystem, present since 2018, and chained it with CVE-2026-123007 to take root on the host. Xint says the chain worked from inside a Docker container, because containers share the host's kernel. It reports tests on AWS, GCP and Azure.

The kernel flaw had no CVE as of Nov. 18, according to Tenable. Xint is withholding most details until a patch exists.

Xint and CIRCL, Luxembourg's Computer Incident Response Center, suggest a stopgap on hosts that do not use SCTP. Add the line "install sctp /bin/false" to a .conf file in /etc/modprobe.d/. That does not unload a module that is already loaded, and it does not disable SCTP built directly into the kernel.

What to do now

Upgrade to 1.31.9 or 1.30.7, then restart NGINX fully or use its live binary upgrade. A reload leaves the old executable running, and existing connections can stay on old worker processes.

Until patched, disabling HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633 only. It does not touch the other three. For the others, Xint's configuration conditions point to these steps:

  • Turn off HTTP/3 to remove the setup CVE-2026-121810 needs.
  • Avoid SSI, mirror and variable-built proxied server names for the resolver flaw. Xint notes that turning off mirror alone does not make a server safe, because other subrequest features may reach the same bug.
  • Restrict mail proxy listeners to trusted networks.

To see whether a server accepts HTTP/2, run openssl s_client with the -alpn h2 option against it. The output reads "ALPN protocol: h2" if it does.

Official Docker Hub images carry the fixed tags. Ubuntu and Debian had not shipped fixed packages as of Nov. 18, according to The Hacker News, and distribution packages can carry a fix without changing the version that nginx -v reports, Xint says. Admins on distro builds need to check each vendor's tracker rather than rely on the version string.

Cycode says the retired ingress-nginx Kubernetes controller bundles NGINX, serves HTTP/2 by default and will not receive a fix. Its guidance is to set use-http2 to "false" in the controller's ConfigMap and plan a move to another ingress controller.

The open item is the kernel half of the chain. Until a patch for the SCTP flaw ships and Xint publishes its details, an attacker who gets code execution as an NGINX worker on an unpatched kernel still has a reported path to root.

Sources used for this briefing

15 links from 15 independent newsrooms (syndicated copies of the same report count once)

These are the sources it draws on, linked so you can verify.

unknown
unknown
unknown
unknown
unknown
unknown
linux.how2shoutNginx Fixes nginx2root: Five RCE Bugs Patched in 1.30.7 and 1.31.9
unknown
blog.ostorlab.coNGINX2Root: Five NGINX RCEs, Fixed in 1.31.9 (CVE-2026-123007) | Ostorlab
unknown
cycodeNGINX2Root (CVE-2026-123007 and four more): unauthenticated remote code execution in nginx - Cycode
unknown
ox.securityNGINX2Root: 5 Critical NGINX RCE Vulnerabilities & CVE Fixes | OX Security
unknown
equixlynginx2root: Disabling HTTP/2 stops two of five nginx RCE flaws | Equixly
unknown
patchmonNGINX2Root (CVE-2026-123007): Patch Your nginx Fleet | PatchMon
unknown
unknown
atlasumnginx's November 2026 Security Release: 1.30.7 and 1.31.9 — Atlas