Particle.news

Five Critical NGINX Flaws Including Decade-Old HTTP/2 Bug Allow Remote Code Execution

Public proof-of-concept exploits and the server’s wide use mean operators must apply vendor patches or disable HTTP/2 as an urgent safety step.

Overview

  • Multiple independent research teams disclosed five critical vulnerabilities in NGINX, with the worst tracked as CVE-2026-123007, an HTTP/2 integer-underflow present since 2015 that can allow unauthenticated remote code execution.
  • F5/NGINX released fixed builds (Open Source 1.31.9 and 1.30.7) the same day the flaws were published and advised administrators to upgrade and fully restart worker processes to remove vulnerable code.
  • Working proof-of-concept exploits are public: Rapid7 demonstrated an HTTP/2-based exploit that needed very large traffic volumes and Xint showed a chain from the HTTP/2 bug to a Linux kernel SCTP flaw that produced host root in tests.
  • Exploitation requires specific runtime configurations—most critically HTTP/2 enabled for the two top bugs—so responders recommend patching first and, when patching is not immediately possible, disabling HTTP/2 or blocking the SCTP kernel module where appropriate.
  • Researchers said multiple teams used AI tools to find the bugs, and the convergent, rapid discoveries plus public PoC code increase the urgency for organizations to shorten their time-to-patch and inventory exposed NGINX instances.