nginx 1.30.7 and 1.31.9: two HTTP/2 bugs that can lead to remote code execution
· Menno-Paul Schreuder
Two nginx HTTP/2 bugs can let an attacker run code on your server without logging in. Which versions fix it, and what to do if you can't update today.
- Security
- Laravel
- Statamic
On 18 November 2026 F5, the company behind nginx, released nginx 1.31.9 and 1.30.7. They fix a batch of security bugs, two of which stand out: memory-corruption bugs in nginx's HTTP/2 code that researchers at Wiz (opens in a new tab) turned into remote code execution in their lab, without logging in. Both are rated 9.2 out of 10 (CVSS v4.0).
If your Laravel application, Statamic site or WordPress site (for now) runs behind nginx, and most self-hosted ones do, this is about you. It's the web server, not your code or PHP, so no composer update or plugin update changes it. The nginx package on the server has to be updated.
What's wrong
HTTP/2 lets a browser send many requests over one connection at the same time. Keeping track of all those streams is where both bugs live.
- Flow-control underflow (CVE-2026-123007 (opens in a new tab)). HTTP/2 has a system where each side tells the other how much data it may send. By sending a large number of these window updates in a particular way, an attacker can make a counter in nginx wrap around, after which nginx writes to memory it shouldn't. According to Wiz this works even on a server that only serves static files over HTTPS, without a backend.
- Use-after-free (CVE-2026-123633 (opens in a new tab)). When nginx passes HTTP/2 requests on to a backend (PHP-FPM, an application server, another proxy) and a worker runs short of connections, it can keep using memory it has already released.
Neither needs an account or a click from anyone. Exploiting them isn't easy (the score's "high attack complexity" says as much), but Wiz did it against the official nginx builds, including a way around ASLR, the protection that normally makes this kind of attack much harder. They haven't published the exploit. When I checked on 19 November, nobody had reported attacks in the wild.
Who is at risk
Every nginx server with HTTP/2 switched on, from version 1.9.5 (CVE-2026-123007) or 1.19.7 (CVE-2026-123633) up to and including 1.31.8. That's nearly every nginx server on HTTPS: HTTP/2 is the default in most server panels and in Certbot-style setups. A quick check from the outside:
curl -sI --http2 https://example.com -o /dev/null -w '%{http_version}\n'
If it prints 2, the server speaks HTTP/2. (Behind a CDN that terminates HTTP/2 itself, this tells you about the CDN, not your server. Wiz says such a CDN or WAF may block parts of the attack, but not that it makes you safe.)
What to do
Update nginx. That's the fix.
- Check what the server runs and where it comes from:
nginx -vand, on Debian or Ubuntu,apt-cache policy nginx. - If nginx comes from nginx.org or you build it yourself: update to 1.31.9 (mainline) or 1.30.7 (stable).
- If it comes from your distribution, don't look at the nginx version number: distributions patch their older version and change only the package revision. On Ubuntu the fixed packages (USN-9159-1 (opens in a new tab)) are
1.24.0-2ubuntu7.20on 24.04 LTS,1.18.0-6ubuntu14.23on 22.04 LTS and1.28.3-2ubuntu1.13on 26.04 LTS. Debian stable and oldstable were still listed as vulnerable when I checked on 19 November; follow the Debian security tracker (opens in a new tab). - Restart nginx after the update (
sudo nginx -t && sudo systemctl restart nginx), then check the version again. Until the old processes are gone, the old code is still running. - On managed hosting or a server panel: ask your host or check the panel's update status, and get a date.
If you can't update today
Turn HTTP/2 off until you can, as Wiz recommends. On nginx 1.25.1 or later, add http2 off; to each server block and remove http2 from the listen lines; on older versions, removing http2 from listen is enough. Then sudo nginx -t and reload.
Browsers fall back to HTTP/1.1 without complaint. Your site gets a little slower on pages with many files, nothing breaks. Switch HTTP/2 back on after updating. If you run HTTP/3 (listen ... quic), switch that off as well: the same release fixes a separate HTTP/3 bug.
What I'd take from this
Last month it was PHP, now it's the web server in front of it. The update is a one-line command. The work is knowing which machines run nginx in the first place: the production server, the staging copy, the forgotten demo box, the Raspberry Pi in the cupboard that serves something to the internet. Make that list this week, and keep it.
Sources: Wiz research (opens in a new tab), nginx security advisories (opens in a new tab), Ubuntu CVE pages CVE-2026-123007 (opens in a new tab) and CVE-2026-123633 (opens in a new tab).