nginx: Critical HTTP/2 Flaw, Update to 1.31.9 Now
nginx has new releases, 1.31.9 and 1.30.7, that fix ten security flaws. The most serious, CVE-2026-123007, sits in HTTP/2 and, according to security firm Rapid7, lets an attacker run code on the server without logging in. It went public on November 18, 2026, and affects versions 1.9.5 through 1.31.8 with HTTP/2 turned on.
What we know
- Fixed versions: nginx.org released 1.31.9 (mainline) and 1.30.7 (stable) on November 18, 2026; its security advisories page lists both as not vulnerable to all ten issues. nginx.org describes the HTTP/2 bug as an overflow that can crash a worker process "or might have potential other impact."
- The main flaw: CVE-2026-123007, memory corruption in HTTP/2 flow control. nginx.org rates it "major" and lists every release from 1.9.5 to 1.31.8 as vulnerable. Xint, the firm that named it "NGINX2Root," says the bug has been there since nginx first added HTTP/2.
- Severity: Rapid7 scores it 9.2 out of 10 (CVSS 4.0). According to The Hacker News, F5, which owns nginx, gives the five main flaws a 9.2.
- Two more "major" issues, per nginx.org: an infinite loop while reading a request body over TLS 1.3 (CVE-2026-118899) and a use-after-free in the mail proxy module (CVE-2026-113425). There are also medium-severity flaws in HTTP/2 (CVE-2026-123633), HTTP/3 (CVE-2026-121810) and the resolver.
- What an attack takes: Rapid7's proof of concept ran code, with the permissions of the nginx worker process, on nginx 1.31.8 in Docker but had to push about 128 GB over HTTP/2. Rapid7 adds that on links slower than roughly 300 Mbit/s, the attack runs into nginx's default one-hour limit per connection.
- Attacks in the wild: neither Rapid7 nor Xint reports any. According to The Hacker News, neither does F5; the same outlet says a public proof of concept exists, limited to a freshly started container on the same machine.
- NGINX Plus: per Rapid7, fixed in 37.3.0.1 and 37.0.8.1; R34 to R36 have no fix.
- Linux distributions: according to The Hacker News, as of November 18 Ubuntu and Debian had not shipped fixed packages, while the official Docker images already offered 1.31.9 and 1.30.7.
What changes and what doesn't
The minimum safe version moves up to 1.30.7 or 1.31.9. The 1.30.6 and 1.31.7 releases from the October security update are no longer enough.
What doesn't change: each flaw depends on configuration. The two HTTP/2 bugs only matter if HTTP/2 is enabled; the mail bug only if nginx proxies email. Rapid7 says HTTP/2 connections that arrive through another proxy are probably not usable for this attack.
One more thing that trips people up: Xint warns that distribution packages can include the fix without changing the version number nginx -v prints.
How to check if you're affected
- See whether your site is served by nginx:
curl -sI https://yourdomain.com | grep -i server. If it saysnginx, the responding server uses it. If it showscloudflareor another CDN, ask what sits behind it: many WordPress and Drupal sites run nginx as the web server or as a proxy in front of Apache. - Shared hosting: you can't patch it yourself. Ask your host whether its servers run nginx 1.30.7 or 1.31.9, or carry the fix for CVE-2026-123007.
- VPS or your own server:
nginx -vshows the version. If nginx comes from your distribution, search the package history for the CVE (apt changelog nginx | grep CVE-2026-123007on Debian and Ubuntu;rpm -q --changelog nginx | grep CVE-2026-123007on Red Hat-based systems). - Upgrade, then fully restart:
nginx -s reloadkeeps the old binary running. Restart the service (systemctl restart nginx) or do a live binary upgrade. - If you can't upgrade today: Xint suggests turning HTTP/2 off temporarily (
http2 off;on 1.25.1 and later, or removehttp2from thelistenline on older versions). That covers the two HTTP/2 flaws, not the rest, and pages may load a bit slower, so switch it back on once you've upgraded. - Check afterwards: the site loads, HTTPS works, and
curl -sI --http2 https://yourdomain.comanswersHTTP/2if you re-enabled it.
Related: nginx Fixes 5 Flaws: Update to 1.30.6 or 1.31.7
Sources
- nginx.org, "nginx security advisories"
- F5, advisory K000163926 on CVE-2026-123007
- Rapid7, "CVE-2026-123007: Critical NGINX HTTP/2 integer underflow leads to RCE (Fixed)," November 18, 2026
- Xint, "NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching," November 18, 2026
- The Hacker News, "10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers," November 18, 2026
Updates: any changes backed by a primary source will be added here.