Nginx patches 10 vulnerabilities including five critical NGINX2Shell flaws
Five critical memory safety vulnerabilities dubbed NGINX2Shell, including two unauthenticated HTTP/2 remote code execution flaws dating back to 2015, have been patched in Nginx 1.30.7 and 1.31.9.
Summary
Nginx has released security updates for its stable (1.30.7) and mainline (1.31.9) branches to address 10 vulnerabilities, five of which are grouped under the NGINX2Shell designation with CVSS 4.0 scores of 9.2. The most severe pair—CVE-2026-123007 and CVE-2026-123633—reside in HTTP/2 processing and can be exploited remotely without authentication, with one flaw present since Nginx 1.9.5 in 2015. Security researchers at Wiz developed proof-of-concept exploits confirming the practical severity of these issues.
The remaining eight vulnerabilities span multiple subsystems: DNS resolver use-after-free, HTTP/3 memory safety, mail proxy module flaws, TLS 1.3 denial-of-service, PROXY protocol NULL pointer dereference, buffer overflow in alias/try_files directives, client certificate validation bypass, and stream module ssl_preread validation gaps. Administrators are advised to upgrade immediately or obtain distribution-patched packages; temporary HTTP/2 disablement mitigates only two of the ten flaws.
NGINX2Shell vulnerability breakdown and affected components
- HTTP/2 flow-control corruption (CVE-2026-123007): Memory corruption from incorrect HTTP/2 flow-control calculations, present since Nginx 1.9.5 (2015), exploitable remotely without authentication.
- HTTP/2 use-after-free (CVE-2026-123633): Triggered when Nginx incorrectly closes an active HTTP/2 connection during request processing; primarily affects reverse proxy deployments, also unauthenticated and remotely exploitable.
- DNS resolver use-after-free (CVE-2026-123634): Memory safety flaw in the DNS resolver subsystem; exploitability depends on resolver functionality being enabled and used.
- HTTP/3 vulnerability (CVE-2026-121810): Memory safety issue in the HTTP/3 implementation; affected only if HTTP/3 is configured and active.
- TLS 1.3 infinite loop (CVE-2026-118899): Denial-of-service condition triggered when reading client request body over TLS 1.3, causing worker process hang without memory corruption.
Why it matters
Nginx powers approximately one-third of all web servers globally, making these vulnerabilities particularly consequential for Linux distribution maintainers who must rapidly backport patches across supported releases. The decade-long presence of CVE-2026-123007 means countless long-term support and embedded deployments may remain exposed until administrators act, while the unauthenticated remote exploitation path places these flaws in the same operational severity class as historically damaging web server bugs. Cloud providers and container registries distributing Nginx base images face particular pressure to refresh their builds promptly.
What to do
- Upgrade Nginx to version 1.30.7 (stable branch) or 1.31.9 (mainline branch), or install security-patched packages from your Linux distribution.
- If you cannot upgrade immediately, temporarily disable HTTP/2 to mitigate two of the critical vulnerabilities (CVE-2026-123007 and CVE-2026-123633).
- Watch for updates from your Linux distribution if you rely on their Nginx packages rather than upstream builds.
Original reference: linuxiac.com →