Cybersecurity Research

Two Critical NGINX Flaws Let Attackers Run Code on Servers With HTTP/2 Enabled

Wiz Research · 19 Nov 2026
Key Takeaway Work out where you run NGINX with HTTP/2 enabled, patch internet-facing servers first, and turn HTTP/2 off if you cannot update straight away.

Several research teams, including Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint, independently found two critical vulnerabilities in NGINX, the web server that handles traffic for more than 225 million websites. The flaws are tracked as CVE-2026-123633 and CVE-2026-123007. Both are rated Critical with a CVSS 4.0 score of 9.2, and both let an unauthenticated attacker run code on the server.

The problems sit in NGINX itself, so a website or API can be exposed even when its own application code is secure. Both flaws require HTTP/2 to be enabled. Wiz reported that its testing of CVE-2026-123007 achieved code execution on NGINX serving ordinary static files, with no backend application or third-party modules involved. Because NGINX often fronts several applications, one affected server can put multiple services at risk. Successful exploitation could allow attackers to take control of the server, steal sensitive data, tamper with websites or disrupt services.

The bugs are old. CVE-2026-123007 is an integer underflow affecting versions back to NGINX 1.9.5 in 2015, while CVE-2026-123633 is a use-after-free that had been present for nearly six years. Wiz says it used its AI code scanning tooling to find both, and AI models to validate their impact. It argues that AI is lowering the barrier to finding complex memory-safety flaws, which shortens the time between disclosure and exploitation. F5, the company behind NGINX, issued a security release and coordinated disclosure on November 18, 2026.

Wiz advises organisations to find affected deployments, prioritise those reachable by attackers, and apply the security updates. If upgrading is not immediately possible, HTTP/2 can be temporarily disabled while patches are tested and rolled out.

Why it matters

Many teams assume that secure application code and a mature, widely trusted web server make the front door low risk, but these flaws sit in NGINX itself and need no authentication or backend application. Anyone running internet-facing NGINX with HTTP/2 is exposed, and a single server may carry several services. The source also suggests that old bugs can surface faster with AI-assisted discovery, so patch speed matters more than a component's long track record.

What to do

  • Identify every NGINX deployment and check whether HTTP/2 is enabled.
  • Apply the F5 security release from November 18, 2026 to affected NGINX servers.
  • Prioritise internet-reachable NGINX servers for patching first.
  • Disable HTTP/2 temporarily on servers that cannot be upgraded immediately.
NGINX CVE-2026-123633 CVE-2026-123007 HTTP/2 remote code execution patch management

Summarised by CISO AI from Wiz Research, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.