Five nginx Memory Flaws Open Different Paths to Remote Code Execution
Technology Policy

Five nginx Memory Flaws Open Different Paths to Remote Code Execution

Five nginx memory-corruption flaws can enable unauthenticated command execution under different HTTP, resolver and mail-proxy configurations. Patched releases are available, but the exposure check must include containers and appliances; researchers demonstrated exploitation without confirming attacks in the wild.

NewTqnia Technology Policy Desk Updated 4 min read
Five nginx Memory Flaws Open Different Paths to Remote Code Execution

Five newly disclosed memory-corruption flaws in nginx can let an unauthenticated attacker crash a worker process or, under the conditions demonstrated by researchers, execute commands with that worker's privileges. The affected paths span HTTP/2, HTTP/3, dynamic proxy resolution and the mail proxy, making configuration as important as the installed version.

The 30-second summary

  • What happened? F5 and nginx.org released fixes for ten nginx vulnerabilities on November 18; researchers grouped five potential remote-code-execution flaws under the name nginx2root.
  • Why does it matter? One flaw requires only an exposed vulnerable HTTP/2 listener, while the others depend on specific proxy, resolver, HTTP/3 or mail settings.
  • What is the catch? Researchers demonstrated exploitation, but CERT-EU and Cloudflare reported no confirmed exploitation in the wild as of November 18.

Key fact: Administrators should update nginx Open Source to 1.30.7 or 1.31.9, or install their distribution's fixed package, and restart the running binary.

Five paths to memory corruption

The broadest flaw, CVE-2026-123007, is an integer overflow in HTTP/2 flow-control accounting. A client can manipulate how nginx adds and returns send-window credit, pushing an internal value past its allowed limit and causing out-of-bounds heap access. Researchers demonstrated command execution against public HTTPS endpoints on major cloud platforms.

CVE-2026-123633 and CVE-2026-121810 are use-after-free bugs affecting HTTP/2 and HTTP/3 proxying when a worker runs short of connection slots. A resolver flaw, CVE-2026-123634, requires a more unusual combination involving variable-based proxy_pass and SSI or mirror subrequests. CVE-2026-113425 affects the nginx mail proxy during an auth_http lookup.

F5 rates all five at 8.1 under CVSS 3.1 and says code execution requires address-space randomization to be disabled or bypassed. The Xint researchers say they found ways to leak memory addresses and bypass that protection in their tested configurations. nginx.org assigns lower severity to several flaws, so the sources differ on practical exploitability even though they agree that patching is required.

Exposure depends on how nginx is reached

An nginx server directly exposed with HTTP/2 is the simplest risk case. Servers using HTTP/3, dynamic upstream resolution or mail proxying need separate configuration checks. Container images, appliances and distribution packages can also carry vulnerable builds even when operators did not install nginx directly.

Cloudflare says origins reachable only through its HTTP proxy are shielded from the HTTP/2 and HTTP/3 attack traffic because the edge terminates those protocols and opens a separate origin connection. That protection does not cover DNS-only records, Spectrum traffic, direct origin access, mail proxying or every resolver configuration. It therefore reduces exposure but does not replace an update.

What administrators should do

NGINX Open Source users should move to 1.30.7 or 1.31.9. NGINX Plus users need a fixed 37.x build listed by F5, while older affected Plus releases require an upgrade path. Distribution vendors may backport patches without changing the short version displayed by nginx -v, so the complete package version and vendor advisory matter.

A configuration reload is insufficient because it does not replace the vulnerable executable already running. Administrators must restart nginx or complete a binary upgrade. Where immediate patching is impossible, disabling unnecessary HTTP/2 or HTTP/3 listeners and restricting mail proxy access can reduce specific risks.

Before we overstate the result

The public evidence establishes working researcher demonstrations, not widespread compromise. None of the five flaws was in CISA's Known Exploited Vulnerabilities catalog in the reviewed material. Worker crashes or processes launched by the nginx account deserve investigation, but a crash alone is not proof that an attacker executed code successfully.

A familiar patching problem at web scale

NewTqnia recently covered Java4Shell's pre-authentication code-execution path and critical PHP flaws affecting web servers. nginx2root creates the same operational challenge: inventories must include hidden copies inside containers and appliances, while mitigations must match the exact protocol and configuration that exposes each flaw.

Verified topics and entities

Sources and citations4 sources

Published by

N

NewTqnia Technology Policy Desk

An institutional editorial team within NewTqnia

A new version of NewTqnia is ready.