Tech

News

Updated

NGINX fixes HTTP/2 flaw present since 2015 that could let attackers run code remotely

Key facts

nginx.org lists versions 1.9.5 to 1.31.8 as vulnerable, and the fixed releases are 1.31.9 mainline and 1.30.7 stable.

What is known

Verified

  • NGINX released the fixed versions 1.31.9 and 1.30.7 on Nov. 18, 2026, and the CVE record lists no workaround.
  • A CISA assessment added to the CVE record at 16:04 UTC on Nov. 18, 2026, recorded exploitation as none.

Not yet known

  • The traffic that triggers the flaw. The CVE record describes it only as undisclosed traffic.

On Nov. 18, 2026, NGINX released 1.31.9 mainline and 1.30.7 stable with fixes for 10 security flaws, among them CVE-2026-123007, a memory corruption flaw in HTTP/2 flow control that the CVE record says could let attackers execute code.

What happened

The nginx.org news entry for Nov. 18, 2026, lists "memory corruption in HTTP/2 flow control (CVE-2026-123007)" among the vulnerability fixes in the two releases. The nginx changelog for 1.31.9 says a flow control window overflow in HTTP/2 might allow an attacker to cause a segmentation fault in a worker process, or might have other potential impact.

The CVE record, filed by F5 and published on Nov. 18, 2026, says the issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the record says, the flow control window can exceed the allowed threshold, which can lead to a heap buffer overflow that is typically followed by a crash of the worker process. The same record says attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. It describes the flaw as a data plane issue only, with no control plane exposure.

The record's CVSS vectors set privileges required and user interaction to none, and the attack vector to network. They also set attack complexity to high.

The numbers

These figures are from the nginx.org security advisories page and the CVE record:

ItemWhat the record saysSource
CVE idCVE-2026-123007nginx.org and CVE record
SeverityMajornginx.org
Vulnerable versions1.9.5 to 1.31.8nginx.org
Fixed versions1.31.9 and later, 1.30.7 and laternginx.org
CVSS 3.1 base score8.1 (High)CVE record
CVSS 4.0 base score9.2 (Critical)CVE record
Weakness typesCWE-191 integer underflow, CWE-787 out-of-bounds writeCVE record

For NGINX Plus, the CVE record lists versions from 37.0.0 up to but not including 37.0.8.1, and from 37.1.0 up to but not including 37.3.0.1, as affected, along with releases from R33.

What the record says comes next

The fix is in NGINX 1.31.9 mainline and 1.30.7 stable, both released on Nov. 18, 2026. The CVE record lists the workaround as "None" and notes that software versions that have reached End of Technical Support are not evaluated. It links F5's advisory, K000163926, as the vendor advisory and patch.

A CISA assessment added to the CVE record at 16:04 UTC on Nov. 18, 2026, recorded exploitation as none, automatable as no and technical impact as total.

Background

The HTTP/2 module, ngx_http_v2_module, first shipped in NGINX 1.9.5 on Sep. 22, 2015, replacing the SPDY module. For the port HTTPS uses by default, see what port HTTPS uses.

The same Nov. 18 releases fixed nine other flaws, according to the nginx.org news entry, including a use-after-free in HTTP/2 (CVE-2026-123633), which nginx.org rates medium and lists as affecting 1.19.7 to 1.31.8. The CVE record credits Stephen Fewer of Rapid7, Tomer Schwartz of Wiz Research, Xint.io and Ikotas Labs with reporting CVE-2026-123007.

NGINX is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy server and mail proxy server, according to nginx.org. For the gateway status code a server can return, see what HTTP 502 means.

Have another question?