nginx HTTP/2 vulnerability: check your server for 1.31.9
nginx 1.31.9 and 1.30.7 fix ten bugs, two in HTTP/2 that can lead to code execution. Check your version, http2 config and container images in minutes.

Quick summary · TL;DR
- **Run
nginx -vandgrep -rnE 'http2|listen .*quic' /etc/nginx/first.** If the version is below 1.30.7 and the grep findshttp2, you're in range for CVE-2026-123007 and should upgrade or switch HTTP/2 off today. - The flow control bug goes back to nginx 1.9.5. Wiz says it got code execution with it on nginx serving plain static files, so a simple setup isn't a safe one. nginx rates it major and Wiz scores it CVSS 4.0 9.2.
- Containers don't get the host's upgrade. Images and ingress controllers are the ones that stay old for months, so run
docker run --rm IMAGE nginx -von every image and check the controller tags too. - A distro package can be fixed without saying 1.30.7. Debian sid's fix is package 1.30.6-4, so compare against the distro tracker rather than the upstream number.
If you run nginx with HTTP/2 switched on, upgrade it this week. nginx 1.31.9 mainline and 1.30.7 stable came out on 18 November 2026 with ten security fixes. Two of them are the nginx HTTP/2 vulnerability people are talking about: memory corruption in HTTP/2 flow control (CVE-2026-123007) and a use-after-free in HTTP/2 (CVE-2026-123633). The first reaches back to 1.9.5, which shipped in 2015.
For a quick check, run nginx -v, then grep your config for http2. Anything below 1.30.7 that speaks HTTP/2 needs the upgrade or the stopgap further down.
What the nginx HTTP/2 vulnerability fix covers
The nginx security advisories page (checked 19 November 2026) lists all ten, and the nginx.org news entry names both releases. Everything from 1.31.9 and 1.30.7 up is fixed.
Which of the ten apply to your config
A plain static site with HTTP/2 on is in range for the first row. Mail and stream bugs reach you only if you run those modules.
| CVE | What nginx says | nginx severity | Vulnerable | Matters if you use |
|---|---|---|---|---|
| CVE-2026-123007 | Memory corruption in HTTP/2 flow control | major | 1.9.5-1.31.8 | HTTP/2 |
| CVE-2026-123633 | Use-after-free in HTTP/2 | medium | 1.19.7-1.31.8 | HTTP/2 with proxying to a backend |
| CVE-2026-121810 | Use-after-free in HTTP/3 | medium | 1.25.0-1.31.8 | HTTP/3 (QUIC) |
| CVE-2026-123634 | Use-after-free in resolver | medium | 0.6.18-1.31.8 | the resolver directive |
| CVE-2026-118899 | Infinite loop reading request body over TLS 1.3 | major | 1.13.0-1.31.8 | TLS 1.3 |
| CVE-2026-113425 | Use-after-free in mail proxy module | major | 0.5.33-1.31.8 | the mail proxy |
| CVE-2026-120993 | NULL pointer dereference with PROXY protocol v2 | minor | 1.31.4-1.31.8 | PROXY protocol v2 (fixed in 1.31.9 only) |
| CVE-2026-125283 | Buffer overflow with alias and try_files | minor | 0.9.6-1.31.8 | alias together with try_files |
| CVE-2026-120967 | SNI bypass with client cert validation in stream | medium | 1.25.5-1.31.8 | stream with client certificates |
| CVE-2026-123640 | Insufficient validation in stream ssl_preread | minor | 1.15.2-1.31.8 | stream ssl_preread |
nginx’s advisory page prints the HTTP/3 ID as “CVE-CVE-2026-121810”, a typo.
CVE-2026-123633 needs three things, per the CVE text on Debian’s tracker: HTTP/2 from the client, requests proxied to a backend, and a worker low on worker_connections. A reverse proxy in front of a dashboard or API fits.
How bad is the nginx HTTP/2 vulnerability
nginx rates the flow control bug major and the HTTP/2 use-after-free medium. Per the CVE text, code execution needs ASLR off or bypassed. Without that, expect a crashed worker.
Wiz’s write-up (18 November 2026) scores both at CVSS 4.0 9.2, the critical range. Wiz says its testing showed code execution on nginx serving ordinary static files, with no backend or third-party module needed, and that it won’t release its proof of concept for now. It doesn’t report any exploitation in the wild. Xint, credited among the reporters, claims on its NGINX2Root page a path from an nginx visitor to root on the host, without giving versions or conditions.
Check your nginx for HTTP/2
Two things decide whether the nginx HTTP/2 vulnerability reaches you: the version, and whether HTTP/2 is on.
1. Version and build.
nginx -v # version only
nginx -V # version plus configure flags
If nginx -V lacks --with-http_v2_module, your build can’t speak HTTP/2, since the HTTP/2 module isn’t built by default. Most distro and official packages include it.
2. Is HTTP/2 or HTTP/3 turned on?
grep -rnE 'http2|listen .*quic' /etc/nginx/
nginx -T 2>/dev/null | grep -n http2
nginx -T dumps the config nginx actually loaded, includes and all, which catches the snippet someone dropped in conf.d years ago. Since 1.25.1 HTTP/2 is a separate directive, http2 on;. On older versions it’s a parameter on the listen line, listen 443 ssl http2;. A listen ... quic line means HTTP/3 is on, and that’s where CVE-2026-121810 applies.
3. Containers and ingress controllers. This is the one people forget. Every image carries its own nginx, and a host upgrade does nothing for them.
docker run --rm IMAGE nginx -v
kubectl get pods -A -o jsonpath='{..image}' | tr ' ' '\n' | sort -u | grep -i nginx
kubectl lists every running image with nginx in the name, which is where ingress controllers and sidecars show up. As with the per-container config in the Docker proxy settings guide, nothing on the host reaches inside the image. Check each tag against the release notes of whoever builds it.
Distro packages and backports
Distros often backport the fix without moving to the upstream number. Debian’s tracker for CVE-2026-123007 shows sid fixed in package 1.30.6-4, a number below 1.30.7.
| Distro | Status on 19 Nov 2026, 10:00 UTC |
|---|---|
| Debian sid | Fixed in 1.30.6-4 |
| Debian forky, trixie, bookworm | Listed as vulnerable, no fixed package yet |
| Ubuntu 22.04, 24.04, 26.04, 26.10 | Fixed, see the Ubuntu CVE page (24.04: 1.24.0-2ubuntu7.20), priority High |
| Ubuntu 16.04, 18.04, 20.04 | Fixed through ESM (Ubuntu Pro) |
| Ubuntu 14.04 | Not affected, its nginx has no HTTP/2 support |
| Red Hat | Lists nginx on RHEL 8, 9 and 10 as affected, no fixed package yet. Rates it Critical, CVSS 3.1 8.1 (draft) on its CVE page |
Compare dpkg -l nginx or rpm -q nginx with your distro’s tracker, daily this week.
Fix the nginx HTTP/2 vulnerability
Upgrade to 1.31.9 or later on mainline, 1.30.7 or later on stable, or your distro’s fixed package. Then make sure nginx actually restarted (systemctl restart nginx), because nginx -s reload only rereads the config and leaves the old binary running.
If a server can’t be patched yet, Wiz and Red Hat give the same stopgap: switch HTTP/2 off. On 1.25.1 and later, set this in each affected server block and remove http2 from any listen line that still carries it:
server {
listen 443 ssl;
http2 off;
}
Older versions only have the listen parameter, so listen 443 ssl http2; becomes listen 443 ssl;. Then test, reload and confirm:
nginx -t && nginx -s reload
curl -sI --http2 https://your-host/ -o /dev/null -w '%{http_version}\n'
You want curl to print 1.1. Wiz also suggests checking that old worker processes have exited, since they keep serving open connections with the old config. Turn HTTP/2 back on once you’ve patched.
NGINX Plus has its own fixed builds, per Wiz: 37.0.8.1 or 37.3.0.1 for CVE-2026-123007 and 37.0.7.1 or 37.2.0.1 for CVE-2026-123633.
Signs worth checking in the logs
Wiz lists general warning signs, not confirmed indicators of these bugs:
- Workers crashing without a reason you know of. In
error.logthat looks likeworker process 1234 exited on signal 11. - Commands launched by nginx, which a web server shouldn’t be doing.
- Long-lived HTTP/2 connections sending a lot of data, since the flow control attack needs many WINDOW_UPDATE frames.
A CDN or WAF that terminates HTTP/2 in front of nginx may partly mitigate it, according to Wiz, depending on how it’s built. Patch anyway.
Why this lands on scraping stacks
nginx usually fronts the tools around a scraper: the results dashboard, the internal API, a self-hosted proxy gateway, a job queue UI. In a typical web scraping architecture each got its nginx config once, often from a template with http2 already on, and nobody has looked since. This is a reverse proxy problem, so patching nginx is the only fix. The rotating residential proxies your scrapers send requests through change the IP a target sees and never touch the nginx box that serves your results. Last week the Apache mod_http2 RCE post ran the same kind of check for Apache.
What to do now
Run nginx -v and the http2 grep on every nginx you run, containers and ingress controllers included, and upgrade the internet-facing ones with HTTP/2 on first. Where you can’t patch today, set http2 off; and recheck with curl.
Frequently asked questions
CVE-2026-123007 is memory corruption in nginx's HTTP/2 flow control, present in versions 1.9.5 through 1.31.8 and rated major by nginx. The CVE text says it can crash a worker, and with ASLR off or bypassed it can lead to code execution. nginx 1.31.9 and 1.30.7 fixed it on 18 November 2026.
nginx 1.31.9 mainline and 1.30.7 stable, both released on 18 November 2026. Any later release is fixed too. Distro packages carry their own numbers (Debian sid fixed it in 1.30.6-4), so check your distro's security tracker.
Run nginx -T and search the output for http2. It shows up either as the http2 on directive or as a parameter on a listen line such as listen 443 ssl http2. To confirm from outside, point curl --http2 with -w '%{http_version}' at your host, and a 2 in the output means HTTP/2 is negotiated.
On nginx 1.25.1 and later, set http2 off in each affected server block and remove http2 from any listen line. On older versions, remove the http2 parameter from the listen lines. Run nginx -t, reload, and check that curl now reports 1.1.
Ubuntu yes, Debian mostly not yet. By 10:00 UTC on 19 November 2026 Ubuntu had released fixed nginx packages for every release from 16.04 to 26.10 (16.04 to 20.04 through ESM), while Debian had a fix only in sid (1.30.6-4). Run apt update and upgrade nginx, then check the trackers again for Debian.
Not according to Wiz, whose 18 November 2026 write-up doesn't report any exploitation in the wild. Its proof-of-concept exploits were built in the lab, and Wiz says it won't release them. Xint, another reporter, claims a path from visitor to root on its NGINX2Root page.
Yes, if HTTP/2 is on. Wiz says its testing showed code execution through CVE-2026-123007 on nginx serving ordinary static files, with no backend needed. The HTTP/2 use-after-free, CVE-2026-123633, is the one that needs proxying to a backend.
Researched and drafted with AI tools, then checked against our publishing rules before it went live: 9 outside links, 5 links to other proxymint pages, no prices and a fact-check pass against our product records. How we write.
