NGINX HTTP/2 Flaws Could Allow Memory Corruption and Remote Code Execution on Web Servers

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Two critical vulnerabilities in NGINX could let remote attackers run code on vulnerable web servers without logging in. The flaws, tracked as CVE-2026-123633 and CVE-2026-123007, were disclosed on November 18, 2026.

Both require NGINX to accept HTTP/2 connections from clients, but the conditions differ. One affects certain reverse proxy setups, while the other can affect a server that does nothing more than serve static files.

The flaws are in NGINX itself, not the websites or APIs behind it. NGINX often handles HTTPS and routes incoming requests to several applications. That means a single vulnerable proxy can put multiple services at risk even when their application code is secure. Depending on what the NGINX process can access, a successful attack could expose sensitive data, alter website content, or interrupt service.

Wiz Research named Ikotas Labs, Metnir, Rapid7, and Xint as independent finders across the two disclosures. Both flaws carry a critical score of 9.2 under the CVSS 4.0 severity scale. The findings show that remote code execution is possible under the reported conditions. They do not, on their own, establish that attackers have used either flaw against production systems.

Netcraft counted more than 225 million sites using NGINX in its September 2026 web server survey. That figure shows how widely the software is used, not how many sites are vulnerable. Exposure depends on the installed version and how the server handles HTTP/2. Multiple sites can also share the same NGINX deployment, so a site count is not a count of affected servers.

These are separate from the NGINX flaws F5 disclosed in October. An organization that applied those fixes may still need another update. F5 lists NGINX Open Source 1.31.8 as affected by CVE-2026-123633, so running a build newer than October’s security release does not mean it contains the November fixes.

NGINX HTTP/2 Vulnerabilities

In its advisory for CVE-2026-123633, F5 describes a use-after-free bug, which means a worker process can reuse memory after it has been released. The issue affects setups where NGINX accepts HTTP/2 client connections and forwards requests to a backend. F5 says the worker must also be running low on available connections. The flaw can crash the worker or, under certain conditions, let an attacker run code.

CVE-2026-123007 has a wider reach. It affects NGINX Open Source releases dating back to 1.9.5, which shipped in 2015. In its disclosure report, Wiz said it demonstrated code execution on an NGINX server serving ordinary static files, with no backend application or third-party modules. A basic site should therefore be part of the patch review, not just API gateways and reverse proxies.

The two November flaws are also distinct from the NGINX HTTP/2 proxy and gRPC vulnerability patched in June, which depended on a different set of configuration options. For this update, administrators should check whether NGINX accepts HTTP/2 from clients. Checking only the protocol NGINX uses to reach a backend can miss the client-facing exposure.

Fixed NGINX versions

The fixes for both flaws are listed for NGINX Open Source 1.31.9 on the mainline branch and 1.30.7 on the stable branch. For NGINX Plus, the minimum fixed builds differ by CVE.

CVE Product Affected versions First fixed versions
CVE-2026-123633 NGINX Open Source 1.19.7–1.30.6 and 1.31.0–1.31.8 1.30.7 (stable), 1.31.9 (mainline)
CVE-2026-123633 NGINX Plus 37.x 37.0.0–37.0.6.1 and 37.1.0–37.2.0 37.0.7.1 and 37.2.0.1
CVE-2026-123007 NGINX Open Source 1.9.5–1.30.6 and 1.31.0–1.31.8 1.30.7 (stable), 1.31.9 (mainline)
CVE-2026-123007 NGINX Plus 37.x 37.0.0–37.0.7.1 and 37.1.0–37.2.0.1 37.0.8.1 and 37.3.0.1
Both CVEs NGINX Plus R-series R34–R36 No fix listed for these releases. Upgrade to a 37.x build that fixes both CVEs.

Administrators should check F5’s CVE-2026-123007 advisory alongside the CVE-2026-123633 advisory and choose a build that covers both. If the current branch has no fix listed, F5 recommends moving to one that does.

Start with internet-facing servers, then check internal proxies and static sites. For NGINX installed through a Linux distribution or bundled with another product, check the supplier’s security notice for the package or image that contains both fixes.

After updating, verify the version actually running on every instance. A configuration reload alone does not replace the running NGINX binary, so restart the service or roll out replacement containers as appropriate.

If a fixed build is not yet available through your update channel, temporarily turn off client-facing HTTP/2 on affected listeners where the service can tolerate the change.

Afterward, test from the client side to confirm the endpoint no longer accepts HTTP/2, and check that websites and APIs still work. Disabling HTTP/2 reduces exposure to these two flaws, but it does not fix the underlying flaws. Install the security update before turning the protocol back on.

What Are Leading Organizations Doing About AI and Cyber Risks? Find Out. View Details!

The post NGINX HTTP/2 Flaws Could Allow Memory Corruption and Remote Code Execution on Web Servers appeared first on Cyber Security News.