Back to Newsroom

NGINX fixes two HTTP/2 flaws as researchers report code execution

Versions 1.31.9 and 1.30.7 contain fixes. The flaws affect different configurations, and vendor severity labels differ from Wiz’s assessment.

NGINX’s November 18 release fixes two flaws in HTTP/2, a protocol used to carry web traffic, as security researcher Wiz reports demonstrating remote code execution in laboratory tests. The software can receive requests for websites and applications, placing the issue in infrastructure that businesses rely on to keep services available.

The official advisory index identifies both mainline version 1.31.9 and stable version 1.30.7 as fixed for the two issues. The broader release includes other security repairs; this report focuses on the HTTP/2 pair.

Two flaws, different conditions

Upstream NGINX advisory comparison
IssueNGINX severityFixed versions
CVE-2026-123633Medium1.31.9 / 1.30.7
CVE-2026-123007Major1.31.9 / 1.30.7

Wiz’s November 18 research says both require HTTP/2 to be enabled. For CVE-2026-123633, it describes a problem in reverse-proxy processing when available connection slots run low. A reverse proxy accepts a user’s request and passes it to an application server. The defect can leave processing dependent on memory that has already been freed.

CVE-2026-123007 concerns HTTP/2 flow control, which regulates how much response data can be sent. Wiz says it demonstrated code execution while NGINX served ordinary static files, without a separate application backend or third-party module. That makes “we only serve static content” an insufficient basis for dismissing this second issue.

What the severity labels establish

The NGINX index rates the first issue medium and the second major. Wiz reports a CVSS 4.0 score of 9.2 for each, calling both critical. Those are separately attributed assessments: the index’s labels do not provide a numeric CVSS score here.

The release notes describe possible worker-process crashes and other potential impact for the flow-control flaw, and a use-after-free condition for the other HTTP/2 issue. Wiz’s stronger code-execution claim comes from its own testing. TrendyVest has not reproduced those tests, and a laboratory demonstration does not establish exploitation against a live business.

What the disclosure means for service operators

The distinction matters when a company measures its exposure. The presence of NGINX establishes a software dependency; it does not, by itself, establish that a vulnerable configuration is reachable. Version, enabled protocol and the way traffic reaches that instance all affect the assessment.

For an affected business, the immediate work can include checking dependencies, testing updates and coordinating changes with service owners. Those activities can consume engineering time without producing a reportable outage. Neither the release nor the research supplies a measured financial loss or a count of affected businesses, so this disclosure cannot support either estimate.

Sources: NGINX release notes and advisory index, plus attributed Wiz research, checked November 18, 2026. Version table covers upstream NGINX; commercial NGINX Plus and distributor-specific packages are outside this report’s verified scope.

More from the Newsroom