nginx vulnerabilities: patch the nginx2root bugs now
Ten nginx flaws were disclosed on November 18, five of them serious memory bugs. Cloudflare says its proxy shields some origins, but you should still update.
On November 18, 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx, the web server software that runs a large share of the internet. Five of them, published under the name nginx2root by the Xint research team, are memory corruption flaws. According to Cloudflare's analysis, an unauthenticated attacker can use them to crash an nginx worker or, per Xint's research, run commands on the server. These nginx vulnerabilities are a patch-now event, even if you sit behind a proxy.
What the five nginx2root bugs are
Each of the five bugs works on its own, and each needs a different configuration to be exploitable. Cloudflare lists them like this:
- CVE-2026-123007: an integer overflow leading to out-of-bounds memory access. It needs HTTP/2 enabled and affects releases back to 1.9.5 (2015).
- CVE-2026-123633: a use-after-free with HTTP/2 and proxy_pass to a backend, when a worker is low on connections.
- CVE-2026-121810: a use-after-free with HTTP/3 (QUIC) and proxy_pass to a backend.
- CVE-2026-123634: a use-after-free involving the resolver, proxy_pass with variables, and a subrequest (mirror or SSI).
- CVE-2026-113425: a use-after-free in the mail proxy when proxy is on and auth_http is used.
F5 rates each one High (CVSS 3.1: 8.1) and Critical (CVSS 4.0: 9.2). Code execution requires disabling or bypassing ASLR, a memory protection built into modern systems. Cloudflare says Xint's write-up shows how CVE-2026-123007 leaked memory addresses to do exactly that. That bug is the one to worry about most, because HTTP/2 is commonly enabled on TLS sites.
The same nginx releases also fix five other bugs. The most serious, CVE-2026-118899, is an infinite loop when reading a request body over TLS 1.3. It lets an unauthenticated attacker stall a worker.
How many servers are exposed
Cloudflare reports that Xint searched Shodan on November 10, before the disclosure, and found 56.7 million hosts matching nginx. Of the 11.94 million that reported a version, 98.9% fell in the affected range. As of November 19, Censys counts about 8.8 million services running a potentially affected version with HTTP/2 enabled.
Version strings do not prove a host is vulnerable, since Linux distributions often backport fixes. Still, the exposure is large.
As of November 19, none of the five CVEs was in CISA's Known Exploited Vulnerabilities catalog, and Cloudflare says it has not seen reports of exploitation in the wild. Xint and Wiz Research have not released their exploits. Rapid7 has published a proof of concept, which it describes as suitable only for demonstrating the attack against a freshly started local container. Cloudflare also warns that fake "exploits" are circulating on GitHub, so be careful about running anything you download.
The Linux kernel bug that makes it worse
Xint also found a use-after-free in the Linux kernel's SCTP send path, present since Linux 4.15 (2018). An attacker who already runs code as the nginx worker can use it to gain root on the host. Xint demonstrated this from an nginx running inside a Docker container, so containers are not a safe boundary here.
Many distributions load the SCTP module automatically the first time a program opens an SCTP socket. That means hosts that never use SCTP can still be exposed. As of November 18, no kernel fix was available, and Xint was withholding details until there is one.
What a Cloudflare proxy does and does not cover
Cloudflare says its own edge is not affected, and that a fix for related code paths in its nginx-based components rolled out globally before the disclosure. This is the vendor's account of its own service, so treat it accordingly.
The more useful claim for site owners is about origins. The HTTP/2 and HTTP/3 attacks need an attacker to send carefully ordered protocol frames straight to the nginx process. When your hostname is proxied through Cloudflare, those connections end at Cloudflare's edge, and the attacker's frames are not forwarded. Cloudflare says this protects against CVE-2026-123007, CVE-2026-123633, and CVE-2026-121810.
There are limits:
- The origin must not be reachable directly. If an attacker finds your origin IP and connects to it, the proxy is not in the path.
- The mail proxy bug (CVE-2026-113425) is not covered, because Cloudflare's HTTP proxy does not carry mail traffic.
- The resolver bug (CVE-2026-123634) is only partly covered. Cloudflare says protection depends on how your config builds proxy_pass.
Cloudflare also notes that some other setups are not protected, and its list of those cases was cut off in the material we reviewed, so read the original post if you use unusual proxy products.
Practical steps to take this week
- Find out which nginx version each of your servers runs, and whether HTTP/2, HTTP/3, the resolver, or the mail proxy is enabled.
- Update to nginx 1.30.7 or 1.31.9, or your vendor's fixed build, then restart nginx.
- If you cannot update right away, consider disabling features you do not need, such as the mail proxy. Cloudflare says many configurations are not vulnerable, but updating or disabling features is the safest way to be sure.
- If you use Cloudflare, make sure your origin accepts traffic only from Cloudflare. Cloudflare suggests Cloudflare Tunnel, a firewall limited to its published IP ranges (at the IP firewall, not in nginx), or Authenticated Origin Pulls.
- Watch for a kernel update from your Linux distribution or host, and apply it when it ships.
- If a hosting company manages your server, ask them in writing whether the nginx fix is installed.
- Do not run "proof of concept" code from unverified GitHub repositories.
If your site runs on WordPress or Formidable Forms and you are not sure what web server sits underneath it, a Formidable Masterminds developer can help you check and patch.
Sources
- nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them The Cloudflare Blog
This post was drafted with AI from the reporting linked above and published by The Jones Foundry. For full details, read the original sources.