NGINX2Root CVE-2026-123007 and CVE-2026-123633: Unauthenticated HTTP/2 RCE With a Public PoC
Introduction
F5 shipped an out-of-band NGINX release on November 18 that fixes ten vulnerabilities. Five of them are CVSS v4.0 9.2 memory-safety bugs that Xint (Theori) named NGINX2Root. The two that matter for nearly everyone are CVE-2026-123007 and CVE-2026-123633 in the HTTP/2 module, both of which give an unauthenticated attacker code execution in an NGINX worker. Rapid7 published a working RCE exploit for CVE-2026-123007 the same day. Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), or NGINX Plus to 37.0.8.1 / 37.3.0.1, and restart the master process.
What Happened
Xint found the bugs on October 11 and reported them to F5 through HackerOne on October 16. Wiz Research, Rapid7, Ikotas Labs and Metnir independently found overlapping issues; Wiz says it used its own AI tooling to do it. F5 published security notification K000164058 on November 18.
The five critical CVEs:
| CVE | Component | Needs | Since |
|---|---|---|---|
| CVE-2026-123007 | ngx_http_v2_module: send_window integer underflow → out-of-bounds copy |
HTTP/2 over TLS | 1.9.5 (2015) |
| CVE-2026-123633 | ngx_http_v2_module: connection use-after-free |
HTTP/2, worst on reverse proxies short of free connection slots | 1.19.7 |
| CVE-2026-123634 | Resolver use-after-free | Request-derived proxy_pass with resolver |
varies |
| CVE-2026-121810 | ngx_http_v3_module use-after-free |
QUIC / HTTP/3 listeners | varies |
| CVE-2026-113425 | ngx_mail_proxy_module use-after-free |
Mail proxy enabled | 0.5.x |
The same release also fixes five lower-severity issues: CVE-2026-118899 (TLSv1.3, 8.7), CVE-2026-120993 and CVE-2026-120967 (ngx_stream_ssl_module), CVE-2026-123640 (ngx_stream_ssl_preread_module) and CVE-2026-125283 (map regex matching).
Exploit status on disclosure day:
- Rapid7 released a public PoC for CVE-2026-123007 that includes a crash trigger and a full unauthenticated RCE, demonstrated against NGINX 1.31.8 in Docker with HTTP/2 over TLS. It is constrained: x86-64 glibc only, around 128 GB of HTTP/2 traffic, and an ASLR bypass is required.
- Wiz confirmed RCE with an ASLR bypass on official 1.31.7 and 1.31.8 builds serving only static files, and is withholding its exploits.
- No in-the-wild exploitation was reported as of November 18, and none of the CVEs were in CISA KEV.
Why It Matters
NGINX sits in front of more than 225 million websites by Netcraft's count. It is also the default Kubernetes ingress in a lot of clusters, the reverse proxy in front of internal apps, and the TLS terminator baked into countless container images and appliances. CVE-2026-123007 needs nothing but HTTP/2 over TLS, which is the default on most modern configs. It does not care whether you proxy to an application or just serve static assets.
Code execution lands in a worker process. That process holds your TLS private keys in memory, sees every request and response in clear text, including session cookies and API tokens, and usually has network reach into the backends it proxies. Xint also disclosed an unpatched Linux kernel SCTP use-after-free that turns worker access into root, which is where the "2Root" name comes from. Today's PoC is noisy and slow, but full exploits for the most widely deployed web server tend to get better quickly.
Who Is Affected
- NGINX Open Source before 1.30.7 (stable) and 1.31.9 (mainline). The earliest affected version depends on the CVE.
- NGINX Plus R33–R36 and 37.x before 37.0.8.1 or 37.3.0.1. R33–R36 get no patch, so you have to move to 37.x.
- Any distro package, container base image (
nginx:*,*-alpine), ingress controller or appliance that embeds an unpatched NGINX build, until its maintainer ships the fix. - Each bug is only reachable if its feature is enabled: HTTP/2 for 123007/123633, QUIC for 121810, the mail proxy for 113425, dynamic
proxy_passwithresolverfor 123634.
How to Protect Yourself
1. Inventory versions and enabled features
nginx -v
nginx -V 2>&1 | tr ' ' '\n' | grep -E 'http_v2|http_v3|mail'
# which listeners have HTTP/2, QUIC or mail enabled
nginx -T 2>/dev/null | grep -nE '^\s*(listen .*(http2|quic)|http2 on|http3 on|mail \{|resolver )'
# containers and Kubernetes ingress
docker ps --format '{{.Names}} {{.Image}}' | grep -i nginx
kubectl get pods -A -o jsonpath='{range .items[*]}{range .spec.containers[*]}{.image}{"\n"}{end}{end}' | grep -i nginx | sort -u
2. Upgrade, then restart the binary
The fixed builds are 1.30.7 / 1.31.9 (OSS) and 37.0.8.1 / 37.3.0.1 (Plus). A nginx -s reload does not replace the running executable, so restart the service:
# Debian / Ubuntu (nginx.org repo)
sudo apt update && sudo apt install --only-upgrade nginx
# RHEL / Alma / Rocky
sudo dnf upgrade nginx
sudo systemctl restart nginx
# confirm the master process started after the upgrade
ps -o pid,lstart,cmd -C nginx | head -3
For images, bump the base tag (for example nginx:1.30.7-alpine) and redeploy. A running pod will not pick up the fix on its own.
3. Stopgaps if you cannot upgrade today
These only cover individual CVEs. They are not fixes:
# CVE-2026-123007 / CVE-2026-123633: turn off HTTP/2 (1.25.1+)
server {
listen 443 ssl;
http2 off;
}
# older versions: remove "http2" from the listen directive
- CVE-2026-121810: remove
quiclisteners. - CVE-2026-113425: bind mail proxy listeners to loopback or firewall them.
- CVE-2026-123634: point
proxy_passat a fixedupstreamblock rather than a request-derived variable.
Turning off HTTP/2 hurts performance, and Xint advises against using it as a blanket workaround. A CDN or WAF that terminates HTTP/2 in front of NGINX may blunt the HTTP/2 bugs, depending on how it forwards traffic. Turn HTTP/2 back on after you have upgraded.
4. Block the kernel escalation path
Xint's SCTP use-after-free has no CVE or patch yet. If a host does not use SCTP, stop the module from loading:
echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf
lsmod | grep -w sctp || echo "sctp not loaded"
5. Hunt for crashes and odd children
The public exploit needs a large volume of HTTP/2 traffic and causes worker crashes along the way:
sudo grep -hE 'worker process [0-9]+ exited on signal (11|6)' /var/log/nginx/error.log*
journalctl -u nginx --since '2026-11-18' | grep -Ei 'signal 11|segfault|core dumped'
# nginx workers should never spawn shells or downloaders
ps -eo pid,ppid,user,cmd --forest | grep -A2 '[n]ginx: worker' | grep -E 'sh|bash|curl|wget|python|nc '
Wiz suggests alerting on long-lived HTTP/2 connections that move unusually large amounts of data, or that send large numbers of WINDOW_UPDATE frames. If you find signs of compromise, rotate the TLS private keys served by that host and any secrets in its upstream configs.
Source
- Tenable — NGINX2Root FAQ: Five vulnerabilities in NGINX (CVE-2026-123007)
- Wiz — Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007
- BleepingComputer — Critical NGINX "NGINX2Root" bugs let attackers hijack servers
- The Register — AI found more critical bugs in another widely used technology running 225M websites