
In mid-November 2026, researchers disclosed NGINX2Root, a cluster of five critical remote code execution (RCE) vulnerabilities in the widely used NGINX web server. The most severe flaw, CVE-2026-123007, is an integer overflow in NGINX’s HTTP/2 flow-control code that lets an unauthenticated attacker execute code as the NGINX worker process when HTTP/2 is enabled. In fact, CVE-2026-123007 has existed since NGINX 1.9.5 (Sept 2015) and was patched in the Nov 18, 2026 update (Open Source versions 1.30.7 and 1.31.9). F5 (NGINX’s parent) released an out-of-band security advisory on Nov 18, fixing these five RCE bugs (and five others). CERT-EU warns that all unpatched NGINX instances with affected features active (especially HTTP/2) must be updated immediately.
Technical Details of the Vulnerabilities
Figure 1: NGINX2Root vulnerabilities found in November 2026. CVE-2026-123007 and CVE-2026-123633 affect NGINX servers using HTTP/2. The blue arrows show possible attack paths.
NGINX2Root covers five security flaws found in different parts of NGINX. Each one affects a specific feature or setup, so not every NGINX server is vulnerable to all five.
- CVE-2026-123007 (HTTP/2 integer overflow): This bug affects how NGINX handles HTTP/2 flow control. If HTTP/2 is enabled, an attacker can send specially crafted HTTP/2 frames that cause a memory error. In most cases, this crashes the NGINX worker process. However, under certain conditions, attackers may also be able to run their own code. Researchers have already shown that this is possible, although the public exploit requires a large amount of data and a way to bypass ASLR, a security feature that makes attacks harder.
- CVE-2026-123633 (HTTP/2 use-after-free): This flaw also affects HTTP/2, but it happens when NGINX forwards requests to a backend server. If the server is running low on memory, an attacker may trigger a memory error while NGINX is closing an HTTP/2 connection. According to F5, this could allow attackers to execute code with the same permissions as the NGINX worker process.
- CVE-2026-121810 (HTTP/3 use-after-free): A similar use-after-free in the HTTP/3 (QUIC) handler, triggered when draining a stream. The server must have HTTP/3 (QUIC) enabled and proxying to an upstream.
- CVE-2026-123634 (Resolver use-after-free): A bug in the DNS resolver logic when using proxy_pass with a backend name derived from request variables, along with an ssi or mirror subrequest on that same name. If so configured, a sequence of requests can free memory prematurely.
- CVE-2026-113425 (Mail proxy use-after-free): In the NGINX mail proxy (ngx_mail_proxy_module), an attacker can exploit a use-after-free during auth_http lookups if an email service is exposed with external authentication configured.
All five bugs allow unauthenticated code execution with the NGINX worker’s privileges. In practice, the HTTP/2 flaws are the most urgent since HTTP/2 is commonly enabled; other bugs require specific features (HTTP/3 or mail proxy or special resolver config) to be active. Crucially, each RCE typically needs ASLR disabled or circumvented to gain code execution. Xint (the researchers who named “NGINX2Root”) and others have confirmed exploits against these bugs, though none appear in the wild so far.
Bacloud Bare Metal Servers deliver powerful, dedicated performance suitable for virtually any use case — from high-traffic applications and big data workloads to virtualization and infrastructure services. Our servers are highly cost-effective and available in multiple global locations, ensuring reliable performance and low latency for your projects worldwide.
Get Bare Metal server
Risk and Impact
The NGINX2Root vulnerabilities are serious because they could allow attackers to take control of vulnerable web servers. Here's what could happen:
- Remote Code Execution: Attackers who successfully exploit these flaws may be able to run commands on the server. They usually have the same permissions as the NGINX worker process. If that process runs as root, they could gain full control of the system.
- Data Exposure: NGINX often handles HTTPS connections, which means it works with sensitive data. If an attacker takes control of an NGINX worker, they may be able to access information such as passwords, session tokens, and other data passing through the server. In some cases, TLS private keys stored in memory could also be at risk.
- Network Pivot: The NGINX proxy typically trusts backend services; a foothold here means deeper access into the network. Combined with a local privilege-escalation (LPE) bug, an attacker can escalate further. Indeed, Xint demonstrated using a separate Linux kernel SCTP bug to gain root from the NGINX worker (even inside Docker). In short, NGINX2Root can lead to full system compromise if left unpatched.
- Service Disruption: Even unsuccessful exploit attempts can crash worker processes, causing outages or degraded service. CERT-EU warns that “worker process … exited on signal” entries in logs may indicate exploit attempts.
Exploit code for these vulnerabilities is already available online. As of November 18, 2026, there were no confirmed reports of attackers using it against real servers. NGINX and CISA also hadn't reported any known attacks. Even so, servers running affected versions should be updated as soon as possible.
Detection and Indicators
Server administrators should check for signs that someone may be trying to exploit these vulnerabilities. Here are a few things to look for:
- Check NGINX logs: Look through your NGINX error logs for unexpected worker crashes or unusual errors. CERT-EU mentions messages like "worker process … exited on signal" as a possible warning sign. However, a crash doesn't necessarily mean the server has been attacked.
- Check your NGINX configuration: Find out which vulnerable features are enabled on your servers. You can use openssl s_client -alpn h2 to check whether HTTP/2 is supported. Also check if HTTP/3 (QUIC), mail proxying, or dynamic proxy_pass and mirror configurations are in use. If your NGINX version is affected and these features are enabled, you should update it as soon as possible.
- Look for unusual activity: Watch for unexpected processes running under the nginx user or attempts to gain root access. For example, if the SCTP kernel module is loaded without a clear reason, it's worth checking. These activities don't always mean someone has broken into your server, but they could signal an attack.
- Use security scanners: Vulnerability scanners and EDR tools may soon add checks for these NGINX flaws. In the meantime, manually check your NGINX version and configuration, and monitor your logs for suspicious activity.
Mitigation and Remediation
The best fix is to upgrade NGINX to a patched version. According to the official advisories and security analyses:
- Apply Patches: Upgrade to NGINX Open Source 1.30.7 (stable) or 1.31.9 (mainline) or later, which include fixes for all five NGINX2Root CVEs. NGINX Plus customers should update to versions 37.0.8.1 or 37.3.0.1 (or newer) to cover these vulnerabilities. Note: old NGINX Plus R33–R36 releases have no patch, so those users must jump to a 37.x release.
- Restart NGINX: Once you've installed the update, restart NGINX to make sure it's running the new version. You can also use NGINX's live binary upgrade feature. Reloading the configuration alone isn't enough, as the old code may still be running.
- Disable HTTP/2 if you can't update yet: If patching isn't possible right away, turn off HTTP/2 on public-facing servers. You can do this by removing http2 from your listen directives or using http2 off;. This helps protect against CVE-2026-123007 and CVE-2026-123633, but it won't fix the other vulnerabilities affecting HTTP/3, DNS resolution, or the mail proxy. You'll still need to update NGINX.
- Disable HTTP/3/QUIC: Similarly, remove or disable any UDP/QUIC listeners to block CVE-2026-121810 (e.g., stop advertising ALPN h3 on TLS 443).
- Harden Mail and Resolver: For CVE-2026-113425, bind any mail_proxy listeners to localhost or firewall them off from untrusted networks. For CVE-2026-123634, avoid using variable-based proxy_pass names and disable mirroring where possible. Tenable notes that pointing proxy_pass to fixed upstreams and turning off mirroring can block this vulnerability.
- Disable SCTP if you don't need it (optional): Xint also suggests disabling the Linux SCTP kernel module on servers that don't use it. This can help protect against a separate Linux vulnerability that researchers used to gain root access in their tests. It's an extra security measure, not a fix for the NGINX flaws.
- Reload or restart NGINX: After changing the configuration, reload NGINX and check that the changes are working. If you've installed a patched version, fully restart NGINX so it runs the updated code. You can also use the openssl ALPN test to confirm that HTTP/2 is no longer enabled.
Conclusion
On November 18, 2026, five serious security flaws were disclosed in NGINX, known as NGINX2Root. The most concerning is CVE-2026-123007, an HTTP/2 bug that could allow attackers to run code on vulnerable servers.
If you're running an affected version of NGINX, update it as soon as possible. The fixes are available in versions 1.30.7 and 1.31.9, as well as newer releases. If you can't update right away, disabling HTTP/2 can reduce the risk, but it won't protect against all five vulnerabilities.
No confirmed attacks in the wild have been reported so far, but proof-of-concept exploit code is already public. That makes patching worth prioritizing, especially for servers exposed to the internet.