Patch-now · Breaking

NGINX patches two critical HTTP/2 bugs, CVE-2026-123007 and CVE-2026-123633, that let attackers with no login run code on web servers; one reaches back to 2015 builds

F5 and the nginx project shipped fixes on Nov 18 for a batch of NGINX memory bugs. The two worst, CVE-2026-123007 and CVE-2026-123633, sit in HTTP/2 handling and can let an unauthenticated attacker run code on the server. F5 rates them 9.2 (CVSS 4.0) and 8.1 (CVSS 3.1). Wiz, Rapid7, Ikotas Labs, Metnir and Xint found them independently. Fixed versions are NGINX Open Source 1.30.7 and 1.31.9. No in-the-wild exploitation has been reported yet.

Nov 18, 2026 · 2 min read

Why this matters. NGINX is the front door for a huge share of the web: it takes HTTPS traffic and routes it to apps and APIs. Wiz says it powers more than 225 million websites. A bug here can expose a site even when the app behind it is written perfectly.

The two critical bugs. CVE-2026-123007 is a math error in HTTP/2 flow control, the part that tracks how much data a client is ready to receive. By cancelling queued data, an attacker can make NGINX copy memory with a bad length. It affects every release from 1.9.5 (2015) through 1.31.8, and Wiz says it can hit NGINX serving plain static files over HTTPS. CVE-2026-123633 is a use-after-free (memory freed while still in use) that bites reverse-proxy setups when connection slots run low. Both need HTTP/2 turned on, which is common. Code runs with the NGINX worker process's permissions.

How bad is it right now. Rapid7 and Wiz both built working proof-of-concept exploits in the lab but have not released them. Wiz notes these memory bugs are hard to exploit remotely and need an extra step to learn memory addresses. Still, five teams found the same area at once, so expect others to follow. The same release fixes more NGINX bugs, including HTTP/3, mail proxy and resolver issues (nginx.org advisory list).

Defender move. Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), or NGINX Plus to 37.0.8.1 or 37.3.0.1; Rapid7 lists no fix for Plus R34 to R36. Run nginx -v to check, and don't forget NGINX bundled inside containers, ingress controllers and appliances. Can't patch today? Turn HTTP/2 off (http2 off; and remove http2 from listen lines), reload and confirm old workers have exited. Watch for unexpected worker crashes.

Sources