Nginx Security Flaws: What Site Owners Must Do

Share this post
4 min read

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.

Key Takeaways.
  • 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.

2015Year of Nginx 1.9.5, the oldest release with the main HTTP/2 flaw, according to nginx.org.

Which Nginx Versions Are Affected

Nginx versionStatusWhat to do
1.31.0 to 1.31.8 (mainline)AffectedUpdate to 1.31.9
1.30.0 to 1.30.6 (stable)AffectedUpdate to 1.30.7
1.29 and olderAffected, no fixMove to 1.30.7 or newer
Nginx Plus R33 to R36Affected, no fixMove to a fixed 37.x release
Nginx Plus 37.0.8.1 or 37.3.0.1FixedNo action needed

Version details come from nginx.org and the Tenable summary of the F5 advisory.

Good to know. Linux distributions often ship fixes under their own package numbers. Check your distribution’s security notice, not just the version number Nginx prints.

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

  1. Check your version by running nginx -v on the server.
  2. Back up your Nginx configuration folder before any change.
  3. Install the update from your package manager or the official Nginx repository.
  4. Test the configuration with nginx -t.
  5. Fully restart Nginx. A reload does not replace the running program.
  6. 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.
Good to know. These steps reduce risk but do not replace patching. Turning off HTTP/2 can also slow your site for some visitors.

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.

Try this today. Log in to your server and run nginx -v right now. Write down the version and compare it with the table above.

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?

  1. Reload the configuration
  2. Fully restart Nginx
  3. 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

Found this useful?

Share this post
Syed Danish

Syed Danish

Syed Danish writes about technology, artificial intelligence and free online tools for Digieh. He explains how everyday software works in simple steps, so anyone can get tasks done faster. Connect with him on LinkedIn.

Articles: 35

Leave a Reply

Your email address will not be published. Required fields are marked *