Security 11084 Published by

NGINX rolled out emergency dual releases on today, fixing ten vulnerabilities in mainline 1.31.9 and nine in stable 1.30.7. Three of the mainline flaws are rated "major," including an HTTP/2 flow-control corruption that can crash worker processes. Some issues still affect versions going back to 0.1.29, so a large share of live deployments remain exposed until updated. nginx urges operators to upgrade immediately to the latest stable or mainline build and avoid intermediate versions.



NGINX Ships Emergency Dual Security Release, Ten Flaws Fixed Across Mainline and Stable

Both 1.31.9 and 1.30.7 went out within minutes of each other on Wednesday, closing three "major" bugs and a pile of memory-corruption holes that stretch back over a decade of versions.

NGINX closed ten security holes in its mainline branch and nine more in stable, both landed today. Two branches moving in lockstep like that isn't everyday. The severity list is longer than usual, with three mainline issues carrying nginx's "major" rating. The rest cover memory corruption, denial-of-service, authentication bypass, and information disclosure.

The exposure window is broad. Per nginx's own advisory, some of these bugs still hit versions going all the way back to 0.1.29, released more than ten years ago. If you're still running something that old, act on it first.

Nginx

Why the three "major" flaws come first

The first major issue is a flow-control window overflow in the HTTP/2 module, tracked as CVE-2026-123007. An attacker can trip a segfault in a worker process, or as nginx phrases it, deliver "potential other impact." The range runs roughly from nginx 1.9.5 through 1.31.8, covering essentially every HTTP/2 deployment out there. Xint.io found it.

The second is an infinite loop triggered while reading request bodies over TLS 1.3 (CVE-2026-118899). Workers can get wedged in that loop and burn CPU until the box crawls. That's a denial of service by sheer exhaustion, hitting versions from 1.13.0 to 1.31.8. Maxim Dounin, nginx's lead developer, wrote the fix.

The third major flaw is a use-after-free in the mail proxy module (CVE-2026-113425). It has the widest footprint of the group, spanning 0.5.33 through 1.31.8, and it can corrupt memory or crash a worker outright. Credit goes to both Xint.io and Dounin.

All three leave workers dead on the floor, which is never a good look for software sitting dead center of internet traffic. It's arguably the most serious category in this release.

The rest of the list

The medium-severity bucket is mostly more use-after-frees. One in the resolver (CVE-2026-123634) fires when the same hostname gets resolved twice at once inside subrequests, ranging from 0.6.18 to 1.31.8. A follow-up pair of HTTP/2 and HTTP/3 use-after-frees (CVE-2026-123633 and CVE-2026-121810) show up only when worker_connections run short. Vexera AI's Albert took the HTTP/2 credit; Xint.io did the HTTP/3 side.

Then there's an SNI bypass in stream client-certificate validation (CVE-2026-120967). Finish the SSL handshake fast enough and certificates get checked against the default server instead of the virtual server you actually asked for. It's a potential auth bypass for TLS-terminating proxies, hitting 1.25.5 through 1.31.8. CERT.PL found it.

The minor-rated issues aren't to be taken lightly, despite the label. The buffer overflow from mixing alias with try_files (CVE-2026-125283) has a scary footprint, from 0.9.6 through 1.31.8, though you'd have to be using that specific directive combo to trip it. The PROXY protocol v2 NULL deref (CVE-2026-120993) is mainline-only, locked to 1.31.4 through 1.31.8, and it wasn't backported to stable because PROXY v2 support only entered mainline in the first place. A validation gap in the ssl_preread module (CVE-2026-123640) could let malformed ClientHello messages slip past security rules, touching 1.15.2 through 1.31.8. BreachX Zero Day Labs' Vivek Parikh spotted that one.

It's not all CVEs in 1.31.9, though. The mainline build also carries a batch of behavioral tweaks, starting with stricter HTTP parsing. Header lines without a colon are now rejected, and chunked bodies with too much framing overhead get turned away. HTTP/3's QPACK table got corrected to match RFC 9204, and unknown flags in HTTP/2 SETTINGS messages are now ignored. There's also a GeoIP overflow fix for out-of-range MaxMind coordinates, plus cookie-parsing and OCSP cache-key adjustments that only bite edge-case setups.

Here's where the two branches diverge. Mainline (1.31.9) shows roughly 18 merged changes on GitHub, while stable (1.30.7) looks almost empty. That's not because nobody works on stable. nginx slams security fixes straight into the stable tree instead of routing them through pull requests, so its "What's Changed" list stays deliberately quiet. The lone non-security line in there is a backported CI update.

nginx's position is simple: stay on either the latest stable (1.30.x) or the latest mainline (1.31.x), never something in between. Both 1.30.7 and 1.31.9 are now the recommended points for their tracks.

Upgrade first. Both releases fix every listed issue, so any version from 1.31.8 and down, plus a chunk of older ones, stays exposed until you move. Prioritize the major flaws, especially the HTTP/2 flow-control corruption, since it touches the broadest set of deployments and can crash workers. If you run TLS-terminating stream proxies, check the SNI bypass and the ssl_preread gap, both of which can defeat client-certificate access controls. And if you serve files through an alias-plus-try_files combo, that wide-reach buffer overflow is worth a look.

The official CHANGES log makes it clear 2026 has been a fast release cycle year for nginx, with the 1.29.x through 1.31.x mainline series each carrying multiple CVEs. This dual release fits the pattern. Mature infrastructure at the center of internet traffic still needs tight update cycles, and this one is a good reminder.

Release release-1.31.9 · nginx/nginx

nginx-1.31.9 mainline version has been released, with vulnerability fixes for use-after-free in resolver (CVE-2026-123634), memory corruption in HTTP/2 flow control (CVE-2026-123007), use-after-fre...

Release release-1.31.9 · nginx/nginx

Release release-1.30.7 · nginx/nginx

nginx-1.30.7 stable version has been released, with vulnerability fixes for use-after-free in resolver (CVE-2026-123634), memory corruption in HTTP/2 flow control (CVE-2026-123007), use-after-free ...

Release release-1.30.7 · nginx/nginx