SecOraLens
CriticalCVE

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

Cyber Security News·Source published ·1 min read

What happened?

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.

Key details

  • Two critical NGINX HTTP/2 vulnerabilities allow unauthenticated remote code execution on vulnerable web servers.
  • CVE-2026-123633 is a use-after-free bug affecting reverse proxy setups with HTTP/2 client connections and low worker connections.
  • CVE-2026-123007 affects NGINX Open Source from 1.9.5 onward and was demonstrated on a server serving only static files.
  • A single vulnerable NGINX proxy can put multiple backend services at risk even if their application code is secure.
  • Netcraft counted over 225 million sites using NGINX in September 2026, but exposure depends on version and HTTP/2 configuration.
  • The findings show remote code execution is possible but do not establish that attackers have used either flaw against production systems.

What is affected?

  • NGINX Open Source 1.19.7–1.30.6 and 1.31.0–1.31.8 for CVE-2026-123633
  • NGINX Open Source 1.9.5–1.30.6 and 1.31.0–1.31.8 for CVE-2026-123007
  • NGINX Plus 37.x versions 37.0.0–37.0.6.1 and 37.1.0–37.2.0 for CVE-2026-123633
  • NGINX Plus 37.x versions 37.0.0–37.0.7.1 and 37.1.0–37.2.0.1 for CVE-2026-123007
  • NGINX Plus R-series R34–R36 for both CVEs with no fix listed

How do I fix or mitigate it?

  1. For NGINX Plus R-series R34–R36, upgrade to a 37.x build that fixes both CVEs
  2. Check supplier security notices for NGINX installed through Linux distributions or bundled products
  3. Restart the NGINX service or roll out replacement containers after updating to replace the running binary

Summarised by SecOraLens from Cyber Security News. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.