Offensive security firm Xint has disclosed NGINX2Root, five remote code execution vulnerabilities in nginx that an unauthenticated attacker can exploit, plus a Linux kernel flaw that lets them escalate to root. The fix is nginx 1.31.9, scheduled for release on 18 November, and every administrator running an exposed nginx should check their servers now.
Key points of NGINX2Root for sysadmins in 20 seconds
- CVE-2026-123007 hits every official nginx release from 1.9.5 to 1.31.8 with HTTP/2 enabled.
- Four more flaws depend on HTTP/3, HTTP/2 to a backend, the mail proxy or
resolverwithmirror. - Chained with an SCTP kernel bug, Xint reached root on the host, even from a Docker container.
- Update to 1.31.9 and restart nginx; disabling HTTP/2 only blocks two of the five flaws.
Spanish security outlet OpenSecurity has covered the research in detail. This piece focuses on what administrators need to do, following the checks and temporary mitigations Xint itself recommends.

The five flaws and the configurations they affect
CVE-2026-123007 is an integer overflow in HTTP/2 flow control. When a stream with queued data is cancelled, nginx returns send credit to the connection window without checking it against the protocol maximum, which eventually leads to out-of-bounds heap reads and writes. The bug has been present since HTTP/2 arrived in nginx 1.9.5 in 2015. The other four are use-after-free bugs: CVE-2026-123634 (resolver, a per-request proxy_pass target and mirror, since 1.13.4), CVE-2026-123633 (HTTP/2 proxied to an upstream, since 1.19.7), CVE-2026-121810 (HTTP/3 proxied to an upstream, since 1.25.0) and CVE-2026-113425 (mail proxy with proxy on and auth_http, since 0.5.15).
Checking version, module and configuration
A server is exposed to CVE-2026-123007 if it runs an unpatched release, the binary includes the HTTP/2 module and HTTP/2 is enabled. Start with the version, then check the module and the configuration:
nginx -v
nginx -V 2>&1 | grep -o with-http_v2_module
sudo nginx -T 2>&1 | grep -nE 'listen.*http2|http2 on'Code language: JavaScript (javascript)
Distribution packages need extra care. Ubuntu 24.04 ships 1.24.0, Ubuntu 22.04 ships 1.18.0 and Debian 12 ships 1.22.1, and security fixes are backported without changing what nginx -v reports. Compare the full package version (for example with dpkg -l nginx) with your distribution’s advisory. To see whether HTTP/2 is reachable from the Internet, run this from an outside machine, and test the nginx host directly if a CDN or reverse proxy sits in front:
echo | openssl s_client -connect example.com:443 -servername example.com -alpn h2 2>&1 | grep ALPNCode language: PHP (php)
Temporary mitigations until 1.31.9
For CVE-2026-123007 and CVE-2026-123633, disable HTTP/2 on affected ports. On nginx 1.25.1 and later, set http2 off; in each affected server block and drop the http2 parameter from listen; on older releases, remove it from listen. Clients fall back to HTTP/1.1, but services that need HTTP/2, such as native gRPC, will break.
listen 443 ssl;
http2 off;
For HTTP/3 (CVE-2026-121810), remove the quic listeners, set http3 off; and send Alt-Svc 'clear', then confirm with ss -lunp that nothing listens on UDP 443. If you use mirror with DNS-resolved per-request targets (CVE-2026-123634), point proxy_pass at fixed upstream groups. If nginx runs as a mail proxy with auth_http (CVE-2026-113425), bind the listeners to localhost or restrict them to trusted IPs at the firewall. Existing connections keep the old configuration until they close, so a service restart may be needed after the reload.
Once 1.31.9 or a patched distribution package is installed, restart nginx or perform a live binary upgrade: a reload does not replace the running executable. For detection, Xint suggests watching for long-lived connections that receive huge volumes while sending little, worker crashes with signal 11 in error.log and, above all, any execve by the nginx user tracked with auditd. A legitimate worker never starts external programs.
Frequently asked questions
Which nginx versions are affected by NGINX2Root?
The main flaw, CVE-2026-123007, affects every official release from 1.9.5 to 1.31.8 with HTTP/2 enabled. The other four depend on configuration and on when each feature was introduced.
Which version fixes it?
nginx 1.31.9. On Ubuntu, Debian and similar distributions, check whether the fix has been backported to the packaged version.
Is disabling HTTP/2 enough?
No. It blocks CVE-2026-123007 and CVE-2026-123633, but not the HTTP/3, mail proxy or resolver-with-mirror flaws.
Does reloading nginx apply the update?
No. You need a restart or a live binary upgrade, because a reload keeps the old executable running.
Sources:
