nginx released 1.31.9 (mainline) and 1.30.7 (stable) on November 18 with fixes for 10 vulnerabilities, including an HTTP/2 flow control overflow, use-after-free bugs in HTTP/2, HTTP/3, the resolver and the mail proxy, and an endless loop over TLS. Every version from 1.30.6 and 1.31.8 down is affected by at least some of them.
If your company runs its own website, API or reverse proxy on nginx, plan an update this week. The nginx project released version 1.31.9 (mainline) and 1.30.7 (stable) on November 18 with fixes for 10 security bugs, and its change log lists them all. Most can crash a worker process. Some “might have potential other impact,” the project’s usual wording for bugs that could lead to more than a crash.
What the update fixes
The nginx security advisories page rates three of the bugs major. The fixes that matter most for a typical company setup:
- HTTP/2 flow control overflow (CVE-2026-123007, major). An attacker can overflow a flow control window and crash a worker process, with possible other impact. Affects nginx 1.9.5 through 1.31.8, which covers almost every HTTP/2 server.
- Endless loop over TLS (CVE-2026-118899, major). Worker processes can get stuck reading a request body over SSL. Affects 1.13.0 through 1.31.8.
- Mail proxy use-after-free (CVE-2026-113425, major). Only matters if you use nginx as a mail proxy. Affects 0.5.33 through 1.31.8.
- Use-after-free in HTTP/2 and HTTP/3 (CVE-2026-123633, CVE-2026-121810, medium). Triggered when
worker_connectionsruns out. - Resolver use-after-free (CVE-2026-123634, medium). Applies when the
resolverdirective is in use and the same name is resolved in parallel subrequests. - Buffer overflow with
try_filesandalias(CVE-2026-125283). Only in certain configurations, per the change log.
The other three fix the stream module: client certificates checked against the wrong virtual server (CVE-2026-120967), a crash with PROXY protocol v2 and dynamic certificates (CVE-2026-120993), and malformed TLS ClientHello messages that could bypass ssl_preread restrictions (CVE-2026-123640). The release also rejects header lines without a colon and chunked request bodies with too much framing overhead.
The nginx project has not said that any of these bugs is being exploited.
What to do
- Update nginx. Move to 1.31.9 or 1.30.7, or your Linux distribution’s patched package once it ships. Then reload or restart nginx so the new binary runs.
- Check the containers. Docker images, ingress controllers and appliances often bundle their own nginx. Rebuild images on the new version and watch each vendor’s release notes.
- Know your exposure. If you can’t update today, the HTTP/2 bug is the one to weigh first, since most public nginx servers have HTTP/2 on. Turning HTTP/2 off is only a stopgap, and it costs performance.
- Hosted services are the provider’s job. If a platform runs nginx for you, its team patches it. Look for their notice.
AI bug hunters are now a steady source of patches
This is our analysis. The nginx change log credits Xint.io on four of the 10 fixes and Vexera AI on a fifth. According to Forbes, Xint found its nginx bugs using OpenAI’s GPT-6.1 Sol and GPT-6 Luna, and cloud security firm Wiz says it found the same flaws separately. That fits this week’s pattern: Java4Shell was found with an AI coding tool in about an hour, and Google showed AI agents turning fresh patches into exploits.
For a small team, the consequence is the gap between a fix and an attack. When several groups find the same bug with the same AI tools, the patch announcement is also a map for attackers. Treat web server updates like browser updates: apply them within days. Last week’s Apache HTTP Server 2.4.71 fix was another HTTP/2 bug, so check both if you run both.
Related: Linux NoisyTCP kernel flaw can crash servers and Puppet Server CVE-2026-115731 is now exploited.
