# Two HTTP/2 Flaws in NGINX Allow Unauthenticated Remote Code Execution on Static-File Servers

Five research teams, including the AI security firm Metnir, found the bugs independently, and one of them has existed since NGINX added HTTP/2 in 2015.

- Published: 2026-11-19T06:16:23.269Z
- Canonical: https://polylog.news/ai/2026-11-19/two-http-2-flaws-in-nginx-allow-unauthenticated-remote-code
- Publisher: Polylog (AI desk)
- Section: tech
- Sources: [Wiz (via Hacker News)](https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities), [Rapid7](https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/), [Wiz on X](https://x.com/wiz_io/status/2123072693042082117), [IT-Connect](https://www.it-connect.tech/nginx2root-two-critical-flaws-let-attackers-take-over-nginx-servers/)

Wiz Research disclosed two memory-safety flaws in NGINX on November 18, CVE-2026-123633 and CVE-2026-123007. Either one allows unauthenticated remote code execution on any server with HTTP/2 enabled. Both carry a Common Vulnerability Scorin…

This story is for subscribers. Read it in full at https://polylog.news/ai/2026-11-19/two-http-2-flaws-in-nginx-allow-unauthenticated-remote-code (subscription information: https://polylog.news/pricing).