News and advice

nginx vulnerabilities: our response and what to do

On November 18, 2026, nginx published fixes for ten vulnerabilities. The most serious affects HTTP/2 and, according to the researchers who found it, can let an attacker run code on a server without signing in. nginx is one of the most widely used web servers and reverse proxies, so many organizations should check their servers.

Status as of November 18, 2026. The nginx deployments that Nuagerie manages, for clients and for our internal tools, have been updated to a fixed version and fully restarted. Our shared hosting platforms run LiteSpeed Web Server, a separate product that these vulnerabilities do not affect, and it is kept up to date. No attacks using these flaws had been reported in the sources reviewed.

On this page

What happened?

The nginx team released versions 1.31.9 and 1.30.7, which fix ten vulnerabilities. nginx.

The security firm Xint groups five of them under the name NGINX2Root. The most serious, CVE-2026-123007, is a memory corruption flaw in how nginx handles HTTP/2 flow control. It has been present since version 1.9.5, released in 2015, according to The Hacker News. Xint says it allows code execution with the privileges of the nginx process, without authentication, and reports having demonstrated it on test servers at major cloud providers. Xint.

nginx rates this flaw "major". F5, which publishes nginx, gives it a score of 9.2 out of 10, according to The Hacker News. The four other flaws in the set involve HTTP/2, HTTP/3, the DNS resolver built into nginx and the mail proxy module. The five remaining fixes are mostly lower severity and concern specific TLS, stream and file-path configurations. nginx, The Hacker News.

Xint also reports a separate flaw in the Linux kernel, not yet fixed, that can be combined with any of these nginx flaws to take full control of the server, including from inside a Docker container. Xint is withholding the details until a kernel fix is available. Xint.

Rapid7 researchers have published a demonstration under specific conditions. As of November 18, no attacks had been reported and the flaws were not listed in the U.S. Cybersecurity and Infrastructure Security Agency (CISA) catalog of exploited vulnerabilities. The Hacker News.

Are your systems concerned?

Any server running a version of nginx earlier than 1.30.7 or 1.31.9 should be considered concerned, whatever its role: website, reverse proxy, load balancer, container or appliance. Some products include nginx without making it obvious, such as control panels and network appliances.

Exposure depends on the features in use. HTTP/2, widely enabled on HTTPS sites, is the main vector. HTTP/3, the built-in DNS resolver and the mail proxy are involved in the other flaws.

The version number alone is not always enough. Linux distributions often fix flaws in their own packages without changing the nginx version number, so check your vendor’s advisory. On November 18, Debian and Ubuntu had not yet published fixed packages, according to The Hacker News. The Hacker News.

Nuagerie’s response

We identified the nginx deployments in the infrastructure we manage, applied the fixed versions and fully restarted the services, so the corrected code is the one actually running.

  • Shared hosting: our platforms run LiteSpeed Web Server, which these nginx flaws do not affect. No action is required on your part.
  • Servers and services we manage: the nginx deployments have been updated and restarted.
  • Servers you manage yourself: the update is your responsibility, unless a service agreement covers it. Our team can help, see below.

What to do on your own servers

  1. Update nginx. Install version 1.30.7 or 1.31.9, or your vendor’s package that includes these fixes.

  2. Restart the service completely. A simple configuration reload leaves the old program running. A full restart or a binary upgrade is needed for the fix to take effect. Xint.

  3. Reduce exposure while waiting for a package. If no update is available yet, disable HTTP/2 and HTTP/3 where your service allows it, avoid DNS resolution at request time and restrict the mail proxy to trusted networks. These measures do not cover all ten flaws and remain temporary. Xint, The Hacker News.

  4. Monitor the Linux kernel fix. If your servers do not use the SCTP network protocol, ask your administrator to prevent its module from loading, as recommended by the Luxembourg CERT (CIRCL), then apply the kernel fix as soon as it is published. The Hacker News.

  5. Do not run demonstration code in production. Unverified exploit code has no place on a production server.

Why ongoing management matters

Five days ago, we covered the SignDrop flaw in Windows and now these nginx flaws. Each disclosure requires the same work: knowing where the affected software runs, reading the advisories, judging which configurations are exposed, scheduling the update and checking that the corrected code is really in place.

An update is only one step. A forgotten server, a reload instead of a restart or a package that is not yet available can leave a system exposed while it appears up to date. For the infrastructure we manage, this follow-up is part of our team’s daily work, so our clients do not have to track every advisory themselves.

Questions? We are here to help

For an existing service, find our contact details on the support page.

If you run your own nginx servers, our team can review them, apply the fixes and set up ongoing follow-up. Discover our managed IT services, our cloud and infrastructure offer and our cybersecurity and backup services, or let’s discuss your needs.

Keep reading