Two Critical nginx HTTP/2 Vulnerabilities: How to Check Your Servers and What to Do

November 18, 2026 - Reading time: 5 minutes

On 18 November 2026, F5 released nginx 1.30.7 and 1.31.9 to fix two critical bugs in the HTTP/2 code. Both can let an attacker with no account run their own code on the server. If you run nginx anywhere, including as the web server or reverse proxy in front of a store, check your version and your HTTP/2 setting today.

What was found

Both bugs are memory-safety flaws, and both need HTTP/2 enabled. Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint reported them independently. Wiz rates each 9.2 out of 10 on CVSS v4.0 in its write-up.

CVE-2026-123007 is an integer underflow in HTTP/2 flow control. When a client cancels a stream that still has queued data, nginx refunds the unused send allowance without checking the protocol's maximum. The counter can then exceed that maximum, a later bounds check wraps around, and nginx ends up copying memory out of bounds. Wiz demonstrated code execution against nginx serving ordinary static files over HTTPS on 64-bit systems, with no backend application or extra modules. The bug dates back to nginx 1.9.5, released in 2015.

CVE-2026-123633 is a use-after-free. An HTTP/2 connection with a half-received request can stay on nginx's list of connections it may close. If nginx runs short of free connection slots while proxying that request to an application server, it can close the connection and free its memory while the request is still using it. This one mostly matters for reverse-proxy setups.

Wiz says it has working exploits and is not publishing them. Neither Wiz nor Prostack reports attacks in the wild as of 18 November.

The nginx security advisories page labels CVE-2026-123007 "major" and CVE-2026-123633 "medium" using nginx's own scale. The 9.2 scores come from Wiz's analysis, so use the vendor advisories linked below when you report severity internally.

Which versions are affected

CVE Affected nginx open source versions
CVE-2026-123007 1.9.5 to 1.31.8
CVE-2026-123633 1.19.7 to 1.31.8

Fixed releases are 1.30.7 on the stable branch and 1.31.9 on the mainline branch. NGINX Plus has its own fixed releases, listed in the Wiz post and F5's advisories. The same release also fixes several other bugs, including an HTTP/3 use-after-free and a mail proxy use-after-free, so the upgrade is worth doing even if you have already turned HTTP/2 off.

Check whether you are exposed

Start with the version:

nginx -v

Then look for HTTP/2 in the full effective configuration:

sudo nginx -T 2>/dev/null | grep -nE 'http2'

You are exposed if the version is in the ranges above and HTTP/2 is on. On nginx 1.25.1 and later that means an http2 on; directive, or a listen ... http2 parameter on older-style configs.

Distribution packages often carry fixes without changing the upstream version number, so a low version number on Debian or Ubuntu does not prove you are vulnerable. Check your distribution's security tracker for the nginx package. At the time of the Prostack post below, Debian had not yet published a fixed package.

Mitigate if you cannot upgrade yet

Wiz recommends turning HTTP/2 off until you can upgrade. Browsers fall back to HTTP/1.1, so sites keep working. Pages that load many files may be a little slower.

On nginx 1.25.1 or later, set http2 off; in each affected server block and remove the http2 parameter from any listen directive:

server {
    listen 443 ssl;
    http2 off;
    server_name example.com;
    # ...
}

Then test the configuration and reload:

sudo nginx -t && sudo systemctl reload nginx

Confirm that the old worker processes have exited, since workers that started before the reload keep serving with the old settings:

ps aux | grep 'nginx: worker'

Turn HTTP/2 back on after the upgrade.

Upgrade

Install 1.30.7 or 1.31.9, or your distribution's fixed package once it exists, then reload nginx and confirm the running version with nginx -v. If you run a CDN or WAF that terminates HTTP/2, it may block parts of an exploit, but Wiz notes that depends on the implementation. Don't treat it as a substitute for patching the origin.

Watch for signs of trouble

Wiz points to unexpected nginx worker crashes and commands launched by nginx as general warning signs. Neither is a confirmed indicator for these bugs. CVE-2026-123007 needs a large number of WINDOW_UPDATE frames, so long-lived HTTP/2 connections that push large volumes of data are worth a look in your logs or network monitoring.

If you host a store on shared or managed hosting

The bug is in nginx, so updating WordPress, Magento, plugins or your own code won't fix it. Ask your host whether their servers use nginx with HTTP/2 and what their patch timeline is. Prostack, a UK host, published a notice saying it turned HTTP/2 off on its nginx-based platform until patches arrive. That is a reasonable template for the question to put to your own provider.

Why this keeps happening

Wiz notes that both bugs sat in the code for years, nearly six years for the use-after-free and more than ten for the underflow, and that AI-assisted code analysis helped find them. Memory-safety flaws used to be expensive to find. Wiz expects the window between disclosure and exploitation to shrink as that cost falls. A fast way to disable a feature, such as one config line for HTTP/2, is worth rehearsing before the next advisory.

Sources

This situation is moving quickly. Check the vendor advisories for current fixed versions and patch status before you act.

About

Hi there! My name is Kevin Earl Gardner. I am a Development Manager and Web Developer and (very) Amateur Content Creator based out of Birmingham, Alabama. I like to blog about coding and streaming.