Skip to content
TrustList
Security advisories

nginx 1.31.9 and 1.30.7 fix ten flaws, including HTTP/2 memory corruption

Editorial

By TrustList Editorial

nginx released mainline 1.31.9 and stable 1.30.7 on 18 November 2026 with fixes for ten vulnerabilities, three rated major: HTTP/2 flow-control memory corruption, a TLS 1.3 request-body loop and a mail proxy use-after-free.

About nginx 1.31.9 and 1.30.7 fix ten flaws, including HTTP/2 memory corruption

nginx 1.31.9 and 1.30.7 fix ten flaws, including HTTP/2 memory corruption

18 November 2026: The nginx project released version 1.31.9 of its mainline branch and 1.30.7 of its stable branch, both carrying fixes for ten vulnerabilities. Three are rated major by the project: memory corruption in HTTP/2 flow control, an infinite loop when reading a request body over TLS 1.3, and a use-after-free in the mail proxy module. Every affected range ends at 1.31.8, so any server on an older build of either branch needs the update.

Not yet independently verified. Versions, severities and affected ranges come from the nginx.org security advisories page and the release line on the nginx.org front page dated 18 November 2026, both read on 19 November. The CVSS score and the NGINX Plus versions come from F5's CVE.org record for CVE-2026-123007, published 18 November. F5's own advisory pages could not be read (they are drawn by script), so the Italian agency's count of 22 flaws across F5 products was not checked, nor were press reports calling five of the flaws code execution paths. No exploitation had been reported on the pages we read. We will update this when it can be confirmed, and remove this note.

The three major flaws

CVE-2026-123007 is memory corruption in the HTTP/2 flow-control code. It affects every version from 1.9.5, the release that introduced HTTP/2 support, up to 1.31.8. Any public site or reverse proxy with HTTP/2 enabled falls within that range. F5's CVE record scores it 8.1 (high): it is a heap buffer overflow that normally crashes a worker process, but F5 says code execution is possible where address space layout randomisation is disabled or bypassed. Only the data plane is exposed.

CVE-2026-118899 is an infinite loop that can occur while nginx reads a client request body over TLS 1.3, which affects 1.13.0 to 1.31.8. A loop of this kind usually means a worker process stops serving traffic, so the practical risk is denial of service.

CVE-2026-113425 is a use-after-free in the mail proxy module, present from 0.5.33 to 1.31.8. It matters only where nginx is configured as an IMAP, POP3 or SMTP proxy, which is rarer than web use but common in some hosting and mail gateway setups.

Seven lower-rated fixes

The advisories page lists four medium-rated issues: a use-after-free in the resolver during response processing (CVE-2026-123634, from 0.6.18), a use-after-free in HTTP/3 (CVE-2026-121810, from 1.25.0), a use-after-free in HTTP/2 (CVE-2026-123633, from 1.19.7), and an SNI bypass when client certificate validation is used in the stream module (CVE-2026-120967, from 1.25.5). Three more are minor: a NULL pointer dereference with PROXY protocol version 2 (CVE-2026-120993, only in 1.31.4 to 1.31.8 and fixed in 1.31.9), a buffer overflow when alias is combined with try_files (CVE-2026-125283, from 0.9.6), and insufficient validation in the stream ssl_preread module (CVE-2026-123640, from 1.15.2).

The release is the second security batch in five weeks. Versions 1.31.7 and 1.30.6, released on 14 October, fixed an earlier group of flaws, and 1.31.8 followed on 21 October.

F5, which owns nginx, published its own advisories on the same day. The Italian national cybersecurity agency said F5's updates cover 22 vulnerabilities across its products, ten of them in NGINX Open Source and NGINX Plus. For NGINX Plus, F5's record for CVE-2026-123007 lists 37.3.0.1 and 37.0.8.1 as the fixed releases.

What operations teams should do

Move every nginx instance to 1.30.7 if you track the stable branch, or 1.31.9 if you run mainline. Packages from operating system distributions often carry a different version number with the fixes backported, so check your distribution's security notice rather than comparing version strings alone. Container images built on official nginx tags need rebuilding and redeploying, and ingress controllers that bundle nginx need their own vendor update.

Where you cannot patch at once, the exposure differs by flaw. Turning off HTTP/2 on a listener removes the main memory corruption path but costs performance, so treat it as a short stopgap. If you do not use the mail proxy, stream ssl_preread or HTTP/3, confirm those modules are not enabled in your configuration. After the upgrade, run nginx -V on each host to check the binary that is actually serving traffic.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in