Skip to content
NewA calmer, faster ZeroHour

Two critical NGINX HTTP/2 flaws allow remote code execution

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

Cyber Security Newsby Guru Baran ()4 min read1
Part of a story covered by 6 sourcesF5 fixes five critical NGINX flaws, two enabling HTTP/2 code executionMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Fixes are in Open Source 1.30.7 and 1.31.9; Wiz showed code execution, but production attacks are not confirmed.

Two critical NGINX flaws, CVE-2026-123633 and CVE-2026-123007, disclosed on November 18, 2026, can crash a worker or let remote attackers run code when the server accepts HTTP/2. CVE-2026-123633 is a use-after-free in reverse-proxy setups when connections are scarce. CVE-2026-123007 reaches Open Source 1.9.5 and was shown executing code on a static-file server. Both score 9.2 on CVSS 4.0. Production exploitation is not established.

Unconfirmed: The disclosures do not establish that either flaw has been used against production systems.

Key facts
  • CVE-2026-123633 affects Open Source 1.19.7–1.30.6 and 1.31.0–1.31.8.
  • CVE-2026-123007 affects Open Source from 1.9.5 through those same unfixed ranges.
  • NGINX Plus R34–R36 have no listed fix; F5 says move to fixed 37.x.
  • Netcraft counted more than 225 million NGINX sites in September 2026, not vulnerable servers.
  • October and June NGINX fixes do not cover these November bugs.
Security assessment · AI, from the articlePublic proof of concept

Impact: Unauthenticated remote code execution or worker crash

ProductAffectedFixed in
F5 NGINX Open SourceCVE-2026-123633: 1.19.7–1.30.6 and 1.31.0–1.31.8; CVE-2026-123007: 1.9.5–1.30.6 and 1.31.0–1.31.81.30.7 (stable), 1.31.9 (mainline)
F5 NGINX PlusCVE-2026-123633: 37.0.0–37.0.6.1 and 37.1.0–37.2.0; CVE-2026-123007: 37.0.0–37.0.7.1 and 37.1.0–37.2.0.1; R34–R36 unfixed37.0.7.1 and 37.2.0.1 for CVE-2026-123633; 37.0.8.1 and 37.3.0.1 for CVE-2026-123007
What to do
  1. 1.Upgrade Open Source to 1.30.7 or 1.31.9 and Plus to a build that fixes both CVEs.
  2. 2.Restart NGINX or replace containers; a configuration reload does not update the binary.
  3. 3.If no fixed build is available, temporarily disable client-facing HTTP/2 on affected listeners.
Analyze CVE-2026-123633 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-123007
+1 related CVE
HTTP/2 heap buffer overflow in NGINX Plus and Open Source
9.2—PoC

From the original article

4 min read at 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.

Cyber Security News

By Guru Baran · cybersecuritynews.com

Read the full article at Cyber Security News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.