The fix is to upgrade to nginx 1.30.7 if you follow the stable branch, or nginx 1.31.9 if you follow the mainline branch. Both are out now and close all five NGINX2Root flaws. They carry 10 security fixes in total, so they also patch several other bugs announced the same day, including an infinite loop in TLS 1.3 request handling.
- Check what you run. On the server, run the command nginx -v. Anything at 1.31.8 or below on mainline, or below 1.30.7 on stable, needs updating.
- Update from where you installed it. If you use nginx’s own packages, pull the new release. If your copy came with your Linux distribution, a container image or a hosting control panel, watch for that vendor’s update and apply it as soon as it lands. Xint warns that only a small share of servers get a fix the moment the new version comes out, so don’t assume an automatic update has already happened.
- Restart and recheck. Reload nginx after the upgrade and run the version check again to confirm the new number.
- Block SCTP if you don’t use it. Until a kernel patch exists, Xint advises blocking the SCTP kernel module on machines that don’t need it, through a module configuration file. That stops it loading in future, but it won’t unload a module that is already running and does nothing if SCTP is built straight into your kernel, so a reboot after the change is the safer path.
Xint says F5 and the big cloud providers, Amazon Web Services, Microsoft Azure and Google Cloud, worked together on the patch before it went public.
Can’t patch tonight? The HTTP/2 stopgap
If you can’t upgrade straight away, the advice from Wiz and Xint is to switch off HTTP/2 in your nginx configuration until you can. That shuts the door on the two worst bugs.
There is a cost. Browsers will quietly fall back to the older HTTP/1.1 protocol, which works fine for most websites, but anything that depends on HTTP/2 will break, including apps that talk to each other through Google’s gRPC framework. Treat it as a short-term fix, not a substitute for the upgrade. The other three flaws need specific features (HTTP/3 with upstream proxying, the mirror setup or the mail proxy), so if you use any of those, read the matching nginx advisory for its own workaround.