Check your version tonight. nginx published ten security advisories on 18 November, and most of the affected range covers every release up to 1.31.8.
nginx -v tells you where you stand. The fix is 1.31.9 on the mainline branch, or 1.30.7 if you track stable.
The one worth understanding
CVE-2026-123007 is memory corruption in HTTP/2 flow control, and nginx’s own severity for it is major.
NVD describes the mechanism. When nginx processes undisclosed traffic, “the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault”.
The record then adds the part that gets lost in the retelling. Attackers can “execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR”.
So the honest version is crash and memory corruption for any server with HTTP/2 enabled, and code execution where ASLR is off or can be bypassed. The CVSS 3.1 score is 8.1 with vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. The AC:H is the qualifier: no credentials are needed, but the attack is not trivial to land. CVSS 4.0 scores it 9.2.
nginx calls it a data plane issue. There is no control plane exposure.
The research post, and what it claims
A write-up published alongside the advisories frames the flaw as unauthenticated remote code execution. That framing is the authors’ claim.
They used CVE-2026-123007 to run commands as the nginx worker inside a container. From there they chained a Linux kernel zero-day in the SCTP subsystem to reach root on the host. They ran the demo on AWS and say the escape also worked with nginx in Docker.
That is a lab demonstration, and it is theirs. The kernel escalation is a separate vulnerability with its own disclosure timeline. The researchers say they are withholding details until a kernel patch exists.
The batch
Three are rated major. Alongside the HTTP/2 bug there is an infinite loop while reading a client request body over TLS 1.3 (CVE-2026-118899, 7.5). The third is a use-after-free in the mail proxy module (CVE-2026-113425, 8.1).
Four are medium. Three score 8.1: use-after-free in HTTP/3 (CVE-2026-121810), in HTTP/2 (CVE-2026-123633), and during response processing in the resolver (CVE-2026-123634). The resolver flaw carries the same ASLR-qualified code-execution note as the headline bug. The fourth is lower, an SNI bypass with client certificate validation in stream (CVE-2026-120967, 4.8).
Three are minor at 5.3. One is a NULL pointer dereference with PROXY protocol v2 (CVE-2026-120993). Another is a buffer overflow with alias and try_files (CVE-2026-125283). The last is insufficient validation in the stream ssl_preread module (CVE-2026-123640).
All ten are fixed in 1.31.9 and 1.30.7. The exception is the PROXY protocol v2 flaw, fixed on the 1.31 line only.
Each needs its own precondition: HTTP/2, the resolver, the mail proxy module, HTTP/3, PROXY protocol v2, TLS 1.3 request bodies, the try_files and alias directives, stream client certificate validation, or ssl_preread. A plain HTTP/1.1 server gains the least from this list, though the ranges are wide enough that most installs still want the upgrade.
nginx’s page prints one identifier as “CVE-CVE-2026-121810”. That is a typo there; the record is CVE-2026-121810.
What these records are not
All ten NVD records are status Received. That means they carry the vendor’s submission, scores and description, and no NVD analysis yet. No exploitation in the wild is reported in any of them.
One limit matters for self-hosters. This is the upstream project’s list. Debian, Ubuntu, Alpine and RHEL build nginx themselves and backport their own patches, and their advisory status for these CVEs was not checked here. Watch your own vendor rather than assuming apt upgrade covers you.
Sources: nginx’s security advisories page, the NVD records for CVE-2026-123007, CVE-2026-118899, CVE-2026-113425, CVE-2026-121810, CVE-2026-123633, CVE-2026-123634, CVE-2026-120967, CVE-2026-120993, CVE-2026-125283 and CVE-2026-123640, plus the researchers’ write-up, all read on 18 November 2026.

