What is nginx2root?
On November 18, 2026, F5 released nginx security updates for five critical vulnerabilities that Xint named nginx2root: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. Each is rated CVSS v4.0 9.2 and can give an unauthenticated attacker command execution with the privileges of the nginx worker process. Xint also found a separate Linux kernel flaw in SCTP that it chained with the nginx bugs to get root on the host, including from inside a Docker container.
The five bugs are independent attack paths, and each one affects a different configuration. That is why the claim that nginx2root is not exploitable everywhere is partly true, and risky to rely on. This post sets out what each path needs, so you can separate real exposure from noise.
Which nginx configurations are exposed to nginx2root?
| CVE | Required configuration | Blocked by HTTP/2 off |
| CVE-2026-123007 | HTTP/2 enabled. No backend or proxy is needed. | Yes |
| CVE-2026-123633 | HTTP/2, with requests forwarded to an upstream server, and worker connection slots running low | Yes |
| CVE-2026-123634 | resolver, a request-derived proxy_pass and mirror (as tested). Other subrequest features, such as SSI, may also reach the bug. | No |
| CVE-2026-121810 | HTTP/3 (QUIC), with requests forwarded to an upstream server | No |
| CVE-2026-113425 | Mail proxy using proxy on and auth_http | No |
- What is true: a server with none of these features, namely HTTP/2, request-time DNS with mirror, HTTP/3 and a mail proxy, is not reachable by any of the five reported paths. Check every server block and listener, not only the main one.
- What the “not exploitable” claim leaves out: CVE-2026-123007 needs only HTTP/2, which is common on internet-facing TLS servers. Xint reports it works against a public HTTPS port on AWS, GCP and Azure, even under normal traffic. Disabling HTTP/2 blocks only two of the five bugs.
- Code execution versus a crash: watchTowr notes that running code, and not just crashing a worker, requires bypassing ASLR. Xint’s exploits include an address disclosure step, so do not count on ASLR as protection.
- The “nginx -v” counts are noisy: Xint’s Shodan data puts 98.9% of nginx hosts that report a version in the CVE-2026-123007 range. Those are version strings only, and do not show whether HTTP/2 is on or the fix was backported.
- Exploitation status: As of November 19, 2026, no exploitation in the wild is reported and none of the five CVEs is in CISA’s Known Exploited Vulnerabilities catalog. Xint has withheld the final exploit steps, but treat the window as short.
Which nginx versions are affected by nginx2root, and which fix it?
| CVE | Affected nginx Open Source versions | Fixed versions |
| CVE-2026-123007 | 1.9.5 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
| CVE-2026-123633 | 1.19.7 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
| CVE-2026-123634 | 0.6.18 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
| CVE-2026-121810 | 1.25.0 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
| CVE-2026-113425 | 0.5.33 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
For NGINX Plus, CVE-2026-123633 is fixed in 37.0.7.1 and 37.2.0.1, and CVE-2026-123007 in 37.0.8.1 and 37.3.0.1, with no fix listed for R-series releases. Plus status for the other three CVEs is unconfirmed, so check F5’s advisory (K000164058).
Ubuntu 24.04 (nginx 1.24.0), Ubuntu 22.04 (1.18.0) and Debian 12 (1.22.1) ship versions inside the affected range, but distributions often backport fixes without changing the version that nginx -v prints.
Compare the full package version with your distribution’s security advisory. Aikido also reports that ingress-nginx is vulnerable to CVE-2026-123633 and will not get a patch, so Kubernetes users should disable HTTP/2 there and plan a move to a maintained ingress.
The Linux SCTP kernel flaw behind nginx2root
The SCTP flaw is a use-after-free in the Linux send path, present since Linux 4.15 in 2018. Chained with any nginx path, it let Xint escape a container and take root on the host, and no kernel fix was available when Xint published. Hosts that do not use SCTP can add install sctp /bin/false under /etc/modprobe.d/, which does not unload an already loaded module or disable built-in SCTP.
How to check your nginx exposure: CVE ID first, then configuration
- Map by CVE ID. Findings for all five CVEs give you one queue, whatever the package name or version string says.
- Use configuration to prioritize. Start with internet-facing servers that have HTTP/2 enabled, then those with proxying, HTTP/3, request-time DNS with mirror, or a mail proxy.
- Do not trust the version alone. Backports hide fixes, and the ranges cover almost every release since 2015.
To check a host, run
nginx -V 2>&1 | grep -- '--with-http_v2_module' for HTTP/2 support, and nginx -T | grep -E 'http2|http3|quic|mirror|auth_http' for enabled features.
How to detect nginx2root in your environment with ArmorCode
1. Ask Anya
Start with Anya, ArmorCode’s AI security champion, where you can ask targeted questions such as:
- Am I impacted by any of these CVEs: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425 ?
- Show me all applications, services, and workloads exposed to nginx2root Vulnerability.
- Am I vulnerable to the nginx2root Vulnerability?
2. Findings Page
- Navigate to the Findings page to access the pre-configured saved view, “nginx2root Nov 2026”. By consolidating results around the CVE ID, it unifies findings from all connected scanners into a single triage workflow. Prioritize remediation by sorting assets according to their criticality and internet exposure.
How to fix nginx2root: update, mitigate by configuration or close connections
- Update to 1.31.9 or 1.30.7 (or the fixed NGINX Plus build), then restart nginx. A configuration reload alone does not replace the running executable.
- If you cannot update, mitigate by configuration. Disable HTTP/2 (http2 off;, or remove http2 from listen on older versions) for 123007 and 123633. Point proxy_pass at a fixed upstream for 123634. Remove QUIC listeners and set http3 off; for 121810. Bind mail proxy listeners to loopback or allow only trusted IPs for 113425.
- Close existing connections. After a reload, old workers keep serving open connections with the old configuration. Restart nginx if workers are still shutting down.
- Watch for compromise. The 123007 attack leaves little in access logs. Look for nginx workers spawning shells or other programs, repeated worker crashes (signal 11), and long-lived HTTP/2 connections with heavy inbound traffic but little outbound.
- Block SCTP on hosts that do not need it, since container isolation is weaker until a kernel fix exists.