AI, Development & Tech News

Nginx closes two HTTP/2 security vulnerabilities involving remote code execution

261119 nginx http2 security vulnerabilities cover image
Skip to table of contents
Contents 3 sections
  1. Which servers are affected?
  2. What this means for you
  3. Sources

The Nginx project released versions 1.30.7 and 1.31.9 on November 18, 2026. Both versions close ten security vulnerabilities. Two of them are in the web server's HTTP/2 component and allow an unauthenticated attacker to execute code on the server. The security firm Wiz rates both at 9.2 out of 10 points (CVSS 4.0, critical), while the emergency response team CERT-EU rates them at 8.1.

The Nginx project itself classifies the first vulnerability as "Major" (high) and the second as "Medium". Nginx can serve a WordPress site directly or sit in front of the application server. Updating WordPress, plugins, or Wordfence changes nothing about this, writes Wordfence, because the flaws lie in the web server itself.

No attacks are known so far: CERT-EU had reported no cases on November 18 in which anyone is exploiting the vulnerabilities. However, Rapid7 has published a working proof of concept for one of the two vulnerabilities.

Which servers are affected?

Nginx versions from 1.9.5 to 1.31.8 are affected, and only if the server speaks HTTP/2. The project lists this on its security advisories page. Wiz demonstrated the first vulnerability on a server that only serves static files via HTTPS.

Security vulnerabilityPrerequisiteAffected fromFixed in
CVE-2026-123007HTTP/2 is active1.9.51.30.7 and 1.31.9
CVE-2026-123633HTTP/2 is active, requests go to a backend server1.19.71.30.7 and 1.31.9

HTTP/2 is only active if the configuration enables it. According to Wordfence, the packages built by the project include the module, whereas a self-compiled server does not include it by default. Linux distributions can fix bugs without changing the version number. The output of nginx -v is therefore not sufficient: compare the full package version with your distribution's security advisory.

A test by Rapid7 shows how quickly an attack can succeed. The proof of concept has to send around 128 gigabytes of HTTP/2 data and took about two and a half minutes in the test; on a 1 Gbit/s connection, Rapid7 expects 17 minutes. Xint reports successful tests on AWS, Google Cloud, and Azure, in one case via a server's public address.

What this means for you

First, clarify who operates your server. If your host maintains the server, you cannot update Nginx yourself. Then read your host's security advisories and ask whether the updates have been applied. According to Wordfence, a scan with Wordfence or the "Site Health" page in WordPress cannot determine this.

Was gilt für deinen Server?
Nginx-Updates 1.30.7 und 1.31.9 vom 18. November 2026
Wo wird deine Seite betrieben?
  • Hoster pflegt den ServerHinweise des Hosters lesen, nach dem Stand der Updates fragen
  • Eigener Server mit Nginx1.30.7, 1.31.9 oder Distributionspaket einspielen, Nginx neu starten
  • Update heute nicht möglichHTTP/2 vorübergehend abschalten, danach updaten
  • CDN vorgeschaltetServer hinter dem CDN und Wege am CDN vorbei prüfen
Die Abschaltung von HTTP/2 schützt nur vor zwei der zehn Sicherheitslücken
Quellen: Nginx, Wiz, CERT-EU, Xint, Wordfence

If you run the server yourself, check the version with nginx -v and install 1.30.7, 1.31.9, or your distribution's package. Then restart Nginx, because according to Xint a reload is not enough. Rebuild containers from a patched image.

If that is not possible today, temporarily disable HTTP/2: remove http2 from the listen lines or, from Nginx 1.25.1 onward, set http2 off; in the server block. Reload the configuration and check that the old worker processes have terminated. This emergency workaround only protects against the two HTTP/2 vulnerabilities; the remaining ones are eliminated only by the update. Afterwards, you turn HTTP/2 back on.

If a CDN sits in front of your server, the public HTTP/2 connection may terminate there. In that case, check the server behind the CDN and every route to it that bypasses the CDN.

How to create a backup before such changes is shown in the lesson Security and Backups in the WordPress course. If you are looking for a different provider, the comparison of shared hosting, cloud, and VPS can help.

The Nginx project released the updates on November 18, 2026.

Sources

Comments

Register and comment.

Continue reading

You might also like

View all articles →