NGINX2Root: Five nginx Vulnerabilities, Starting With CVE-2026-123007

mse major security alert blog
emma-stevens-bio-portrait
Written by Emma Stevens
Senior Threat Intelligence Advisor

Key takeaways for CVE-2026-123007

  • Xint's NGINX2Root research covers five nginx vulnerabilities. Xint rates them all Critical, and each one can lead to remote code execution (RCE) in the right configuration.
  • The worst is CVE-2026-123007. An unauthenticated attacker can run commands as the nginx worker process, but only if HTTP/2 is enabled.
  • F5 lists nginx Open Source fixes in 1.30.7 and 1.31.9, and NGINX Plus fixes in 37.0.8.1 and 37.3.0.1. Distributions sometimes backport fixes, so check your package's advisory too.
  • Turning off HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633, but not the other three.
  • Xint also chained the nginx bugs with a separate Linux kernel SCTP flaw to get root on the host. No kernel patch was available at publication.

NGINX2Root: What happened?

Xint researchers found CVE-2026-123007 while getting ready for ZeroDay Cloud 2026. A few days later, an automated Xint scan turned up the other four. Xint reported all five to F5 through HackerOne on October 16, and F5's nginx team had them by October 27. Patch validation wrapped up on November 10, and Xint published its writeup on November 18.

How CVE-2026-123007 works

HTTP/2 uses flow-control windows to limit how much data a server can send. Xint found that nginx can let one of those windows grow past its maximum. The memory-copy length calculated from it then becomes invalid, which causes out-of-bounds reads and writes on the heap. Xint used this to leak memory addresses and overwrite a function pointer, which let it run commands as an nginx worker. The writeup leaves out the final reproduction steps. The bug goes back to nginx 1.9.5, the first release with HTTP/2 support.

The other four CVEs

Per Xint's configuration table:

  • CVE-2026-123634 is a use-after-free in the DNS resolver. Xint's test setup used a proxy_pass that takes its destination from the request, along with the resolver directive and mirror with mirror_request_body off. Other features that create subrequests may hit the same bug, so turning off mirror alone may not be enough. Xint identifies nginx 1.13.4 as the first affected release on this path.
  • CVE-2026-123633 is a use-after-free in HTTP/2 connections that forward requests to an upstream server. F5 says this path requires a low worker_connections value. Turning off HTTP/2 blocks it. Xint identifies nginx 1.19.7 as the first affected release.
  • CVE-2026-121810 is a use-after-free in HTTP/3 requests forwarded to an upstream server. Turning off HTTP/2 doesn't block it. Nginx 1.25.0 is the first affected release.
  • CVE-2026-113425 is a use-after-free in the mail proxy's auth_http login path, with proxy on in Xint's test setup. Nginx 0.5.15 is the first affected release on this path, and F5's affected-package range starts at 0.5.33.

Understanding severity and exposure

  • F5's record lists CVE-2026-123007 as CVSS 8.1 (High) under CVSS 3.1. Rapid7 scores it 9.2 (Critical) under CVSS 4.0. F5 says code execution is possible when ASLR is disabled or an attacker can bypass it.
  • Xint says it demonstrated unauthenticated RCE with nginx worker privileges. It also says it confirmed exploitation over public HTTPS endpoints on AWS, GCP, and Azure.
  • Bitsight Threat Intelligence hasn’t identified reports of exploitation in the wild as of publication. 

Where things stand: Patching and mitigations

F5 lists nginx Open Source fixes in 1.30.7 and 1.31.9, and NGINX Plus fixes in 37.0.8.1 and 37.3.0.1. Restart nginx after updating. A reload alone doesn't replace the running binary. Distributions often backport fixes without changing the version nginx -v reports. Xint's example is Ubuntu 22.04, where the binary can still say 1.18.0 after security updates. Compare the full package version with your distribution's advisory.

If you can't update right away, Xint suggests these temporary mitigations. They can break things, so test them first.

  • HTTP/2 (CVE-2026-123007 and CVE-2026-123633): On 1.25.1 and later, add http2 off; to each affected server block and remove http2 from its listen lines. On 1.9.5 through 1.25.0, just remove http2 from listen. gRPC and anything else that needs HTTP/2 may stop working.
  • Request-time DNS lookups (CVE-2026-123634): Point proxy_pass at a fixed upstream group. Xint says mirror_request_body on stopped its test exploit but doesn't fix the resolver bug.
  • HTTP/3 (CVE-2026-121810): Remove the QUIC listeners, add http3 off;, and send Alt-Svc: clear.
  • Mail proxy (CVE-2026-113425): Restrict the mail proxy to trusted networks, either by binding listeners to loopback or using a firewall. F5's advisory has its own guidance.
  • SCTP: On hosts that don't need SCTP, add install sctp /bin/false to a file in /etc/modprobe.d/. That stops modprobe from loading it, but it won't unload a module that's already loaded or disable SCTP built into the kernel.

Treat these as stopgaps and install the fixed release for your branch as soon as you can.

How do I check my exposure?

Run these four checks on each host:

  1. Version. Run nginx -v 2>&1. Versions 1.9.5 through 1.31.8 contain the vulnerable code. F5 lists 1.30.7 and 1.31.9 as fixed. If your distribution packages nginx, check the full package version against its advisory.
  2. HTTP/2 module. Run nginx -V 2>&1 | grep -q -- '--with-http_v2_module' && echo 'HTTP2_MODULE=present' || echo 'HTTP2_MODULE=absent'. If the module is absent, the binary isn't affected by CVE-2026-123007.
  3. HTTP/2 in the config. Run sudo nginx -T 2>&1 | sed 's/#.*//' | grep -nE 'listen[[:space:]].*http2|^[[:space:]]*http2[[:space:]]+on[[:space:]]*;'. This reads the config on disk, so a change you haven't reloaded won't show up.
  4. Reachable from outside. From a machine outside your network, run openssl s_client -connect {HOST}:443 -servername {HOST} -alpn h2 </dev/null 2>&1 | grep -E 'ALPN protocol:|No ALPN negotiated|Connection refused|connect:errno|handshake failure'. Replace {HOST} with your domain. If a CDN or proxy sits in front of nginx, test the nginx server directly as well.

An unpatched server with the HTTP/2 module and HTTP/2 enabled needs action. Don't test production servers with public exploit code. Xint says an attack may leave little trace in access logs, because the HTTP/2 control frames it uses aren't logged as requests. It suggests looking for several signs together: a long-lived connection receiving a lot of data, gaps between bytes received and logged request lengths, nginx workers starting shells or other programs, and repeated abnormal worker exits. Each one can have an innocent explanation, so check them in context.

How Bitsight can help

  • Bitsight AI Mode is available on eligible plans. Its Assess Emerging CVE Exposure workflow lists CVEs Bitsight first detected on your organization in the last 90 days, ranks them, and recommends fixes. It can do the same for a portfolio of your vendors.
  • Bitsight Security Posture Management helps security teams find internet-facing assets and assess their exposure.
  • Bitsight Vulnerability Detection helps identify vendors and assets using NGINX who may be vulnerable. 

Wrapping up

NGINX2Root pairs an HTTP/2 flaw that gives RCE as an nginx worker with a separate SCTP kernel bug that can get an attacker root on the host. Check your nginx versions and HTTP/2 exposure, apply mitigations where you can't patch yet, and install the fixed release for your branch.

NGINX2Root: What to do next

  • Check nginx versions and HTTP/2 status on every host and container image.
  • Apply the temporary mitigations that fit your setup.
  • Install nginx 1.30.7 or 1.31.9, or the NGINX Plus fix for your branch, then restart nginx.
  • On hosts that don't need SCTP, block the module and watch for a kernel patch.
  • Review the other four CVEs against your configuration.
  • Monitor your critical vendors for usage of NGINX and evidence of patching.
Bitsight cta background color
2026 gartner magic quadrant cover

Bitsight Recognized as a Visionary in 2026 Gartner® Magic Quadrant™ for Cyber Threat Intelligence Technologies

Get the report and see why Bitsight was named a Visionary.

 

Download

Bitsight cta background color