NGINX Fixes Two HTTP/2 Flaws That Could Enable Remote Code Execution
NGINX released versions 1.30.7 and 1.31.9 to address two flaws in its HTTP/2 implementation. Researchers in a laboratory demonstrated unauthenticated remote code execution.

NGINX HTTP/2 fixes introduce versions 1.30.7 and 1.31.9, released on November 18, 2026. They address vulnerabilities CVE-2026-123007 and CVE-2026-123633 in the HTTP/2 protocol implementation. Researchers from Wiz said they successfully demonstrated unauthenticated remote code execution for both flaws in laboratory conditions.
According to CERT-EU, no exploitation of these vulnerabilities had been reported in the wild as of November 18. However, operators of internet-facing servers with HTTP/2 enabled should check the version in use and deploy the available fixes.
NGINX HTTP/2 fixes address memory corruption and use-after-free
CVE-2026-123007 is a memory-corruption flaw in the HTTP/2 flow-control mechanism. It affects NGINX Open Source versions 1.9.5 through 1.31.8 when HTTP/2 is enabled. An F5 advisory warns that under certain conditions, it could lead to remote code execution.
Researchers from Wiz demonstrated exploitation of this flaw against a server that provided static content. This means the laboratory scenario did not require the server to operate as a reverse proxy to an application.
The second corrected flaw is CVE-2026-123633, classified as a use-after-free in HTTP/2. Wiz also demonstrated unauthenticated RCE for this flaw in a laboratory. However, according to available information, a practical attack requires a reverse-proxy scenario with an upstream server.
In its security advisories, NGINX states that versions 1.30.7 and later in the 1.30 branch, as well as versions 1.31.9 and later in the 1.31 branch, are not vulnerable.
The risk affects servers with HTTP/2 enabled
If successfully exploited, an attacker could execute code with the privileges of the NGINX worker process. The impact could therefore extend to websites, APIs, and data served by the server. These are flaws in the web-server or reverse-proxy layer, before the web application itself.
The success of a practical attack depends on the specific version, build, and configuration. For CVE-2026-123633, the presence of an upstream server in a reverse-proxy scenario is also required. Severity assessments differ among sources, so they cannot be directly compared without knowing the methodology used.
Updating is recommended; disabling HTTP/2 can help temporarily
The most direct measure is to update to NGINX 1.30.7 or 1.31.9, or to a newer release of the relevant branch. Operators should also verify whether updated packages are already provided by their Linux distribution or cloud-image provider.
If immediate updating is not possible, temporarily disabling HTTP/2 on exposed listeners mitigates the risk of both flaws. This measure does not replace patching, but it removes the condition common to the listed vulnerabilities.
When monitoring operations, it is also useful to watch for unexpected crashes of NGINX worker processes. Crashes alone, however, are not evidence of successful remote code execution. Particularly important will be any confirmed reports of exploitation in the wild and the availability of fixed packages for individual platforms.
Sources
- nginx security advisories – Confirms the CVE identifiers, vulnerable version ranges, and fixed NGINX Open Source versions.
- NGINX news – Confirms the release of NGINX 1.30.7 and 1.31.9 on November 18, 2026, and the list of fixed vulnerabilities.
- F5 K000163926 – Describes the impact of CVE-2026-123007 on NGINX configurations with HTTP/2, including possible remote code execution.
- Wiz Research – Documents the RCE demonstrated by the researchers, exploitation conditions, version ranges, and available mitigations.
- CERT-EU Security Advisory 2026-022 – Reports no known exploitation in the wild as of the publication date and recommends urgent updating.
Verified and updated: 11/19/2026 06:22



