Unauthenticated remote code execution in Nginx

1445 points · 610 comments on HN · read original →

Points and comments are a snapshot, not live.

Two critical unauthenticated RCE flaws in Nginx HTTP/2, patched in versions 1.30.7 and 1.31.9.

Wiz Research and four other teams independently discovered two memory-safety vulnerabilities in Nginx's HTTP/2 handling: CVE-2026-123633 (use-after-free) and CVE-2026-123007 (integer underflow). Both are rated 9.2 CVSS and allow unauthenticated remote code execution on servers with HTTP/2 enabled. CVE-2026-123007 affects versions back to 1.9.5 from 2015. The vulnerabilities exist in Nginx itself, not in proxied applications. Wiz used AI tools to discover the flaws. F5 released patches in Nginx 1.30.7 stable and 1.31.9 mainline. The recommended workaround is to disable HTTP/2 until patching is possible.

The disclosure timeline ran from October 21 to November 18, 2026.

What commenters are saying

Commenters widely agree that patching is urgent, with many expecting exploits to appear quickly given the level of detail in the disclosure. A recurring sentiment is that the complexity of HTTP/2 makes such vulnerabilities unsurprising. Several users noted that while upstream fixes are available, major distros like Ubuntu and Debian have not yet released updated packages. One thread highlighted the unusual number of independent discoverers (five teams), speculating that AI tools may have enabled parallel discovery. Some commenters advocated for rewriting critical infrastructure in memory-safe languages, citing long-standing patterns of memory-safety flaws. The workaround of disabling HTTP/2 is seen as relatively straightforward.