nginx2root: remote code execution in nginx HTTP/2, HTTP/3, resolver and mail proxyPatch

CVE-2026-123007 · CVE-2026-123633 · CVE-2026-123634 · CVE-2026-121810 · CVE-2026-113425

Five memory corruption flaws in nginx, together called nginx2root, can let an unauthenticated attacker crash a worker process or run code on the server, each in a different configuration.

上次審核

更新

  1. F5 (opens in new tab) and nginx.org disclosed ten nginx vulnerabilities fixed in nginx 1.30.7 and 1.31.9 (opens in new tab), including the five Xint calls nginx2root, and Xint published technical details (opens in new tab).

概觀

細節

On November 18, 2026, F5 and nginx.org disclosed ten nginx vulnerabilities. Xint, which reported five of them, published technical details on those five under the name nginx2root. Each is an independent path to memory corruption in a worker process, in a different configuration. F5 rates each one High (CVSS 3.1 score 8.1) and Critical (CVSS 4.0 score 9.2), and says code execution requires ASLR to be disabled or bypassed. Xint describes leaking memory addresses to bypass it.

CVE-2026-123007 is an overflow in HTTP/2 flow control that leads to out-of-bounds heap reads and writes. It affects any server with HTTP/2 enabled, from nginx 1.9.5. Xint demonstrated command execution against a public HTTPS endpoint on AWS, GCP and Azure, and notes that the HTTP/2 control frames the attack uses are not logged as requests.

CVE-2026-123633 and CVE-2026-121810 are use-after-free flaws in HTTP/2 (from 1.19.7) and HTTP/3 (from 1.25.0) when nginx proxies requests to a backend and a worker runs low on worker_connections. F5 says exploiting the HTTP/3 flaw also depends on conditions beyond the attacker's control. CVE-2026-123634 is a use-after-free in the resolver when proxy_pass uses variables and an SSI or mirror subrequest resolves the same name. CVE-2026-113425 is a use-after-free in the mail proxy; Xint reports it with auth_http, triggered during login without valid credentials.

Code execution is Xint's claim: it reports remote code execution with worker privileges for each flaw in its tests. Some of its exploits needed more than reaching nginx. For CVE-2026-123633 and CVE-2026-121810, nginx had to be able to open a TCP connection to the attacker, and for CVE-2026-123634, nginx's resolver had to reach the attacker's DNS server.

The sources differ on scope and severity. F5 and nginx.org list the resolver flaw from 0.6.18 and the mail proxy flaw from 0.5.33, while Xint gives 1.13.4 and 0.5.15 as the first releases for the paths it tested. nginx.org rates CVE-2026-123007 and CVE-2026-113425 major and the other three medium. F5 also credits other researchers for CVE-2026-123007 and CVE-2026-123633.

The same releases fix five further nginx vulnerabilities. The most serious, CVE-2026-118899, is an infinite loop while reading a request body over TLS 1.3 that lets an unauthenticated attacker stall a worker process, in nginx 1.13.0 and later. nginx.org rates it major and F5 rates it High (CVSS 3.1 score 7.5). nginx.org rates the other four medium or minor; most affect the stream modules, and one, CVE-2026-120993, is fixed only in 1.31.9.

Xint also reports a use-after-free in the Linux kernel's SCTP send path, present since v4.15, which it chained with CVE-2026-123007 to gain root on the host, including from nginx in a Docker container. It is withholding the details until a kernel fix is available.

As of November 18, none of the five is in CISA's Known Exploited Vulnerabilities catalog. Xint omitted the final exploitation steps, and the sources reviewed do not report exploitation in the wild.

風險

Any nginx reachable directly from the Internet is at risk. Xint reports running commands as the nginx worker on HTTP/2 servers; F5 says that requires bypassing ASLR.

受影響的部署

NGINX Open Source before 1.30.7 or 1.31.9, and NGINX Plus 37.x before 37.0.8.1 or 37.3.0.1 (37.0.7.1 or 37.2.0.1 for CVE-2026-123633), that use HTTP/2, HTTP/3, proxy_pass with variables together with SSI or mirror, or the mail proxy. F5 lists NGINX Plus R33 and later R releases as affected, with no fixed build.

Distribution packages and container images can carry backported fixes without changing the version nginx -v reports, so check the full package version against your distribution's advisory.

建議操作

Update nginx to 1.30.7 or 1.31.9, or your vendor's fixed build, and restart it. Until then, keep nginx reachable only through Cloudflare's proxy and disable affected features you don't need.

  1. Find every nginx instance, including NGINX Plus, distribution packages and container images. Run nginx -V and nginx -T on each, and note which use HTTP/2, HTTP/3 or QUIC listeners, proxy_pass with variables plus SSI or mirror, or a mail block with proxy on. If a CDN or reverse proxy sits in front, test HTTP/2 against the nginx server directly.

  2. Update NGINX Open Source to 1.30.7 or 1.31.9, NGINX Plus to 37.0.8.1 or 37.3.0.1, or your distribution's patched package. Then restart nginx or complete a binary upgrade, because a configuration reload does not replace the running executable.

  3. If you can't update yet, disable the features you don't need. For CVE-2026-123007 and CVE-2026-123633, set http2 off on nginx 1.25.1 and later, or remove http2 from listen directives on older versions. For CVE-2026-121810, remove QUIC listeners and set http3 off. For CVE-2026-123634, point proxy_pass at fixed upstream groups; setting mirror_request_body on is not a fix. For CVE-2026-113425, limit mail proxy listeners to trusted networks. Restart nginx so existing connections close. On hosts that don't use SCTP, install sctp /bin/false in /etc/modprobe.d/ blocks the kernel module from loading, but doesn't unload a loaded module or disable one built into the kernel.

  4. Verify that each running nginx reports a fixed version, or that its package includes your distribution's fix. Where you disabled HTTP/2, check that openssl s_client -alpn h2 no longer negotiates h2.

  5. Check for signs of exploitation: programs started by an nginx worker, for example with an auditd execve rule on the worker UID, repeated worker crashes such as signal 11, and long-lived HTTP/2 connections whose received bytes grow while logged requests stay small. Investigate any program started by a worker immediately.

將此提示與可檢查您基礎架構的代理程式配合使用。

Assess whether the nginx instances available to you are affected by the nginx2root vulnerabilities disclosed on 2026-11-18: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. Perform a read-only assessment within your authorized access. Do not send exploit traffic, change configuration or restart services.

1. Read F5's index at https://my.f5.com/manage/s/article/K000164058 and its per-CVE articles, https://nginx.org/en/security_advisories.html and https://xint.io/blog/nginx2root-remote-code-execution. Record the vulnerable and fixed versions for each CVE, including your distributions' backports.
2. List every nginx instance, including NGINX Plus, distribution packages, container images and appliances. For each, capture nginx -V, the full package version, and whether nginx itself is reachable from the Internet rather than only through a CDN or proxy.
3. From nginx -T, check each instance for: HTTP/2 on any listener (CVE-2026-123007); HTTP/2 with proxy_pass to a backend (CVE-2026-123633); proxy_pass with variables plus SSI or mirror (CVE-2026-123634); QUIC or HTTP/3 listeners with proxy_pass (CVE-2026-121810); a mail block with proxy on (CVE-2026-113425). Also note TLS 1.3 listeners for the separate denial-of-service flaw CVE-2026-118899, fixed in the same releases.
4. For each instance and CVE, report affected, fixed, not affected or unknown, with the evidence, and note mitigations in place, such as disabled features, restricted mail listeners or a blocked SCTP module.
5. Report any exploitation indicators you can see, such as programs started by nginx workers or repeated worker crashes, and any access gaps that kept you from deciding.

Find more information and resources at https://radar.cloudflare.com/zero-wire/nginx2root

Cloudflare coverage

Service status

Cloudflare reviewed its systems against these vulnerabilities before disclosure. The proxy that handles customer traffic at Cloudflare's edge is based on a heavily modified nginx fork, and an update that closes the related code paths finished rolling out globally before the vulnerabilities were published. Cloudflare is updating the remaining internal systems that use nginx and has restricted access to them in the meantime. Customers do not need to take any action for traffic served through Cloudflare's proxy.

Product coverage

If your nginx can only be reached through Cloudflare's HTTP proxy, with proxied DNS records, you should be safe from these attacks while you update, because Cloudflare terminates client HTTP/2 and HTTP/3 connections at its edge and opens its own connection to your origin. This does not apply to Spectrum TCP or UDP applications or DNS-only records, where the attacker's traffic reaches your origin, or to a mail proxy, which Cloudflare's HTTP proxy does not carry. The resolver flaw depends on how your configuration builds proxy_pass, so update regardless. These are protocol and memory-safety flaws that WAF rules cannot reliably match, and Cloudflare has not released a managed rule for them.

Evidence and sources