Nginx Security Flaws: What Site Owners Must Do

Last updated November 19, 2026
Nginx released urgent fixes on November 18, 2026, for serious web server flaws. If you run your own server, update to 1.30.7 or 1.31.9 and restart it today.
- The worst flaw affects servers with HTTP/2 turned on and needs no login to attack.
- Fixed versions are Nginx 1.30.7 for the stable branch and 1.31.9 for the mainline branch.
- A public proof of concept already exists, so waiting is risky.
- If your host manages the server for you, ask them to confirm the patch.
What Happened
Nginx is one of the most widely used web servers. On November 18, 2026, the project published fixes for several flaws, listed on its security advisories page.
Researchers nicknamed the five worst bugs NGINX2Root. F5, the company behind Nginx, rated each of them 9.2 out of 10, Tenable reported.
The most urgent one, CVE-2026-123007, is a memory bug in HTTP/2 handling. It can let an attacker run code on a server without logging in, per the official record.
Which Nginx Versions Are Affected
| Nginx version | Status | What to do |
|---|---|---|
| 1.31.0 to 1.31.8 (mainline) | Affected | Update to 1.31.9 |
| 1.30.0 to 1.30.6 (stable) | Affected | Update to 1.30.7 |
| 1.29 and older | Affected, no fix | Move to 1.30.7 or newer |
| Nginx Plus R33 to R36 | Affected, no fix | Move to a fixed 37.x release |
| Nginx Plus 37.0.8.1 or 37.3.0.1 | Fixed | No action needed |
Version details come from nginx.org and the Tenable summary of the F5 advisory.
Are You Affected as a Site Owner
You Run Your Own Server
If you manage your own cloud machine or private server with Nginx, you must patch it yourself.
You Use Managed or Shared Hosting
Your host controls the web server. Ask support whether their Nginx servers are patched to 1.30.7, 1.31.9 or a fixed vendor build.
Your Site Runs on Apache or LiteSpeed
These flaws are in Nginx only. Still, some hosts and content delivery networks place Nginx in front of other servers, so it is worth asking.
Who manages the web server for your site?
- I manage it myself
- My hosting company does
- A developer or agency does
- Not sure
How to Patch Nginx Step by Step
- Check your version by running nginx -v on the server.
- Back up your Nginx configuration folder before any change.
- Install the update from your package manager or the official Nginx repository.
- Test the configuration with nginx -t.
- Fully restart Nginx. A reload does not replace the running program.
- Run nginx -v again to confirm the new version.
Tenable notes that a configuration reload keeps the old program in memory. Only a full restart loads the fixed code.
Free updates
Join the Digieh list
Be the first to know when our weekly brief launches.
No spam. Unsubscribe anytime. Read our Privacy Policy.
Stopgaps if You Cannot Patch Today
- Turn off HTTP/2 with http2 off, which covers the two HTTP/2 flaws only.
- Remove HTTP/3 listeners if you use them.
- Limit mail proxy listeners to trusted addresses.
- Use a fixed upstream group in proxy settings instead of names built from variables.
Full stopgap details are in F5’s official advisory. Some steps depend on your exact setup.
Plan Your Patch Window
Digieh built this calculator to help small teams plan. Enter how many servers you run and how many minutes each update takes.
Total time to patch your Nginx servers
Other Security Basics to Check
A patch day is a good time to tighten other weak spots. Strong admin passwords matter, and our guide on how to create strong passwords covers the basics.
Storing many logins? Read how to set up a password manager for your team.
Google also shipped new tools this week. Our news on Gemini 4 Neon notes its separate cyber defense program.
Safety rules are changing too. See what California’s proposed rules would change for big developers.
Test Yourself
After updating Nginx, what must you do for the fix to take effect?
- Reload the configuration
- Fully restart Nginx
- Clear your browser cache
A reload keeps the old program running. A full restart loads the patched version.
Frequently Asked Questions
What is NGINX2Root?
It is the nickname researchers gave to five serious Nginx flaws fixed on November 18, 2026.
Which Nginx version fixes the flaws?
Nginx 1.30.7 for the stable branch and 1.31.9 for the mainline branch.
Are attackers already using these flaws?
There were no confirmed reports of attacks as of November 18, Tenable said. A public proof of concept exists, so that could change quickly.
Editor’s Note
This article is accurate as of November 19, 2026. Details come from nginx.org, the official vulnerability record, F5 and Tenable. Digieh will update this story if attacks are confirmed.
Spot an error in this article? Please contact us at support@digieh.com or read our Corrections Policy.
Keep exploring
Your next read is waiting
1EcommerceHoliday Return Policies 2026: Deadlines at Big Stores4 min read
2InsuranceHome Insurance Claim Steps That Protect Your Payout8 min read
3GamingHow to Choose a Gaming Monitor, Specs Explained8 min read
4Education & CareersHow to Take Notes With the Cornell Method8 min read
5Parenting & FamilyHow to Childproof Your Home, Room by Room8 min read
6NewsWhat Causes a Nationwide Blackout? The Simple Explanation6 min readFound this useful?












