November 19, 2026
NGINX2Root Explained: 5 Nginx Flaws
Five serious Nginx bugs were fixed on November 18, 2026. Here is who is at risk, which versions are safe, and what to do today.

By Emilyharbord
4 min read
On November 18, 2026, F5 and the Nginx team released fixes for a group of serious Nginx bugs. Security researchers call them NGINX2Root.
If you run Nginx on a server, a container, or behind a hosting panel, this matters. The fix is simple, but one small step is easy to miss; you must restart Nginx after the update.
What is NGINX2Root?
NGINX2Root is the name researchers at Xint (Theori) gave to five serious Nginx bugs. It also covers a separate Linux kernel bug that can be chained with them to gain root access. The name is not used by F5 or nginx.org.
The five Nginx bugs are memory bugs. They affect:
- HTTP/2
- HTTP/3
- The DNS resolver
- The mail proxy module
F5 rated all five 9.2 out of 10 on the CVSS v4 scale.
The most urgent bug
CVE-2026โ123007 is the one to worry about most. It needs only HTTP/2 over TLS to be turned on. An attacker does not need to log in.
The flaw dates back to HTTP/2 support in version 1.9.5, released in 2015. The affected code dates back to version 1.9.5. Use the fixed version for your release branch; stable 1.30.7 already includes the fix.
Wiz Research showed that attackers could run commands on a server that only hosted static files. Even a basic Nginx website could be at risk.
Is it being used in attacks?
As of November 18, there were no confirmed reports of real-world attacks. This is a dated status, not proof that no attacks have happened since. The bugs are also not in the CISA Known Exploited Vulnerabilities list as of November 18.
Public test code is available for CVE-2026โ123007, but using it is difficult. It needs about 128 GB of network traffic, a specific x86โ64 server setup, and a way around ASLR, a security feature that protects memory. The attack is also unlikely to work when a proxy handles HTTP/2 connections before they reach Nginx.
Still, a public exploit means defenders should not wait.
Which versions are fixed?
The following versions include fixes for the five NGINX2Root flaws. Check which version you use and update to the fixed release for your branch.
- Nginx stable: 1.30.7 or later
- Nginx mainline: 1.31.9 or later
- NGINX Plus: 37.0.8.1 and 37.3.0.1
These releases include fixes for the five NGINX2Root flaws. They do not mean a server is safe from every security issue.
Compare the version inside your own branch. For example, 1.31.8 is affected, while 1.30.7 is not, even though 1.31.8 is the higher number.
Some older NGINX Plus releases (R33 to R36) have no patch. Those users need to move to a 37.x release.
Five Other Bugs Fixed in This Update
The same release also fixed five more Nginx flaws. They include a TLS 1.3 problem (CVE-2026โ118899), a buffer overflow involving alias with try_files, and issues in stream handling.
Updating to the fixed versions covers all ten.
How to Fix NGINX2Root
Patching is the full fix. Turning off a feature only reduces risk for the bugs tied to that feature.
1. Update Nginx
Install Nginx 1.30.7 or 1.31.9 or newer from your package source. If you use a Linux distribution package, check your distribution's security notice.
Some distributions fix the bug without changing the version number that nginx -v shows. For example, on Ubuntu 22.04 the binary can still say 1.18.0 after a security update.
2. Test the configuration and restart Nginx
This step is the one people miss. A reload (nginx -s reload) applies config changes but keeps the old program in memory. The old, flawed code stays running until you restart.
On a systemd-based server, test the configuration first. Restart only if the test passes:
sudo nginx -t && sudo systemctl restart nginxsudo nginx -t && sudo systemctl restart nginxA restart may briefly interrupt traffic. Plan for this if the server handles live services.
3. Check other software that uses Nginx
Products that include Nginx, such as OpenResty and some Kubernetes ingress controllers, need their own updates. Ask the vendor or check the project.
The Kubernetes ingress-nginx project was archived in March 2026 and does not ship new releases. Qovery advises removing it and moving to a supported option.
Temporary Protection for Unpatched Nginx Servers
These steps are temporary. Each one covers only some of the bugs.
Turning off HTTP/2 will make clients fall back to HTTP/1.1. Services that need HTTP/2, such as gRPC, will stop working, so test first.
What to Check in Your Linux Kernel
Researchers also found a separate bug in SCTP, a network feature in the Linux kernel. Combined with the Nginx bugs, it could let an attacker gain root access and take full control of the server. It could also let an attacker break out of a Docker container and reach the host.
As of November 18, the kernel bug had no patch or CVE tracking number. Check your Linux provider for newer updates. The Nginx update does not fix this bug.
If your server does not use SCTP, blocking its module is a temporary option. But blocking it from loading will not stop it if it is already running. It also will not disable SCTP if it is built into the kernel. Check your Linux provider's latest security advice before making changes.
Install the kernel fix when it becomes available, and reboot if required.
Quick Checklist
- Run
nginx -vand check the full package version. - Update to 1.30.7 or 1.31.9, or the fixed package from your vendor.
- Restart Nginx. Do not rely on a reload.
- Check products that include Nginx, such as OpenResty and ingress controllers.
- Block SCTP on servers that do not need it.
- Install the kernel patch and reboot when it is released.
Final thoughts
NGINX2Root is serious because Nginx is everywhere, and the worst bug sits in a common feature, HTTP/2. The good news is that fixed versions are out and the steps are short: update, restart, and check your other Nginx-based tools.
Note: If you use Laravel Forge, its automatic security updates do not patch Nginx. You need to update it yourself. For the steps, you can check this guide on updating Nginx on Laravel Forge.