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_passthat takes its destination from the request, along with theresolverdirective andmirrorwithmirror_request_body off. Other features that create subrequests may hit the same bug, so turning offmirroralone 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_connectionsvalue. 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_httplogin path, withproxy onin 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.