The nginx team announced on November 18, 2026 that it has released mainline version nginx-1.31.9 and stable version nginx-1.30.7 of the widely used web server and reverse proxy. Version 1.31.9 fixes 10 vulnerabilities, and 1.30.7 fixes nine. The most notable is CVE-2026-123007, an HTTP/2 flow control issue rated "major" on the official advisory list, with an unusually wide affected range of 1.9.5 through 1.31.8.

An HTTP/2 Flow Control Flaw Can Let Attackers Crash Workers

According to the nginx.org changelog, CVE-2026-123007 is an overflow of the HTTP/2 flow control window (the limit on how much data a peer can accept). The changelog says it "might allow an attacker to cause a segmentation fault in a worker process, or might have potential other impact." Xint.io is credited with reporting it.

The official security advisory list gives the vulnerable range as 1.9.5 through 1.31.8, with 1.31.9 and later and 1.30.7 and later not vulnerable. In other words, for configurations that use HTTP/2, nearly every version released over many years falls within scope. The nginx.org changelog does not specify what the "potential other impact" might be.

A second HTTP/2 vulnerability, CVE-2026-123633, was also fixed. It is a use-after-free that can occur when worker_connections (the per-worker connection limit) is not sufficient. It is rated "medium," with an affected range of 1.19.7 through 1.31.8.

Ten Fixes in Total, Covering HTTP/3, Mail and the Stream Module

The fixes in this release go well beyond the two HTTP/2 issues. The main ones are listed in the table below.

CVEDescription
CVE-2026-123007HTTP/2 flow control window overflow
CVE-2026-123633Use-after-free in HTTP/2
CVE-2026-121810Use-after-free in HTTP/3
CVE-2026-125283Buffer overflow in certain configurations using "try_files" and "alias"
CVE-2026-123634Use-after-free during name resolution with "resolver"
CVE-2026-113425Use-after-free in the mail proxy
CVE-2026-120967In the stream module, client certificates may be verified with a configuration other than the one selected by SNI
CVE-2026-123640ngxstreamsslprereadmodule may interpret malformed ClientHello messages differently from other implementations
CVE-2026-118899Worker may enter an endless loop while reading the request body over SSL
CVE-2026-120993Segmentation fault when using PROXY protocol v2 with dynamic certificate loading

The fix for CVE-2026-120993 is included only in 1.31.9 and does not appear in the 1.30.7 changelog. The other nine are fixed in both versions. Because whether many of these issues apply depends on configuration, administrators need to check them against the features their own deployments use.

Advisories Are Hosted on F5's Support Site, With No Standalone Patches

The nginx.org security advisory list points to articles on F5's support site for the advisory on each vulnerability. The advisory for CVE-2026-123007 is K000163926, and the one for CVE-2026-123633 is K000163928. Meanwhile, the entries for this release do not include links to standalone patch files.

As a result, even environments that build from source will generally need to update to 1.31.9 or 1.30.7. Those using packages from a Linux distribution should check each distributor's status as of this writing.

Administrators of Public Servers With HTTP/2 Enabled Should Update

The greatest impact falls on web servers and reverse proxies that expose HTTP/2 to the internet. CVE-2026-123007 can be triggered by traffic sent by an attacker, so servers that accept connections from outside are in scope. Repeated worker crashes could make a service's responses unstable.

Our Take

The discovery of a flaw that has persisted across long-used versions suggests that HTTP/2 implementations are still being actively probed as attack targets. With the official changelog leaving "potential other impact" open, it would be risky to assume the worst case is just a crash. That said, fixed releases are already available on both the stable and mainline branches, so updating is enough to address it. On the other hand, nginx is often embedded in products and appliances, and in those environments there may be a delay while waiting for vendors to ship updates.

Summary

On November 18, nginx released 1.31.9 and 1.30.7, fixing vulnerabilities including an HTTP/2 flow control flaw (CVE-2026-123007). Any deployment running 1.9.5 or later is in scope, especially public servers with HTTP/2 enabled. Advisories for each vulnerability are hosted on F5's support site, and the first step is to update to a fixed release.

Sources: