NGINX code execution bug explained: idle-connection race and HTTP/2 bandwidth budget integer overflow
arpit_bhayani · x · 2026-11-19
A deep-dive into two memory-safety exploit paths for a new NGINX code execution vulnerability.
- Connection cleanup race: NGINX keeps an idle connection pool it can prune under slot pressure. A connection can be marked idle right as a request starts using it; NGINX misses this, closes it anyway, and frees memory still in active use. An attacker can get that freed memory reallocated with their own data and hijack the running request.
- Bandwidth budget overflow: HTTP/2 gives each connection a send budget. On request cancellation NGINX returns unused budget without checking the ceiling, letting attackers inflate the count past its limit; the oversized number later overflows into a wrongly sized buffer, enabling out-of-bounds reads/writes, memory leaks, and eventual code execution.
The author notes both bugs are memory-safety issues rather than logic mistakes — dangerous, but genuinely instructive exploits.
Related event: nginx2root: Unauthenticated RCE Chain in nginx Escalates to Root(9 posts)→
More from Infra
- Musk denies Anthropic scrapped SpaceX compute deal, says it may want 10GW more — teortaxesTex · 2026-11-19
- DuckDB and Hugging Face workshop turns 2.1M Amazon reviews into an API in one afternoon — JeremyCMorgan · 2026-11-19
- FAA to Replace 1980s Floppy-Disk Weather Displays at 435 Facilities by 2028 — alvelda · 2026-11-19
- TokenWing offloads 60% of MoE experts to SSD, 120B at 50 tok/s on a laptop — Grawnch · 2026-11-19
- Microsoft's Maia200 chip enters mass production with 1.7x tokens-per-watt gain — 创业邦 · 2026-11-19
- Janas and Colibri Run 80B MoE Models on a Mini PC and Colab's L4, Why No Hype? — Chrono_Tri · 2026-11-19