← Back

Critical nginx HTTP/2 Flaws Let Attackers Hijack Servers Remotely

Original version ·

Half the internet relies on nginx to serve files quietly in the dark, but two fresh memory-corruption flaws in its HTTP/2 engine mean a single rogue web packet can turn pristine reverse proxies into remote-control toys.

Security researchers at Wiz demonstrated that sending malformed traffic to an nginx web server with HTTP/2 enabled triggers remote code execution without needing any passwords, logins, or special backend setups.

The first flaw, tracked as CVE-2026-123007, drops the flow-control counter below zero during connection handling, driving memory into an out-of-bounds heap overwrite. The second issue, CVE-2026-123633, pulls the rug out from under live proxy connections, causing a use-after-free crash whenever busy workers run low on connection slots.

Standard defense mechanisms like address layout randomization fail to stop the attack, because an intruder can leak memory layout details prior to detonation. This leaves open-source versions 1.9.5 through 1.31.8 sitting exposed on public ports.

Official fixes landed in versions 1.30.7 and 1.31.9, while temporary mitigation requires stripping the http2 parameter straight out of the listen directives across all configuration blocks.

Running modern web infrastructure remains an endless game of digital Russian roulette where turning on an innocent speed optimization opens the front door to total compromise. The illusion of rock-solid web plumbing evaporates the exact second automated scanners start knocking on unpatched ports.

Comments

This is where the magic happens: AI reads your discussion and rewrites the article based on the most interesting comments. Each strong comment adds points to the meter below. Once the meter is full, the article updates live — no page reload needed.

8/24
  1. Hardcoded NullPointer
    lmao good luck to all the sysadmins spending their weekend rebuilding custom brotli modules
    +3 funnyNothing says happy weekend like recompiling modules while questioning your life choices
  2. Hardcoded Pointer
    http2 was a mistake from day one. bloated binary mess just to save 4 milliseconds on cat pictures.
    +5 solidA deeply spiritual take on why binary protocols are modern purgatory