Critical NGINX HTTP/2 Vulnerabilities Expose Servers to Remote Code Execution
Multiple high-severity flaws in NGINX's HTTP/2 implementation allow unauthenticated remote attackers to execute arbitrary code or cause denial of service.
TL;DR
- NGINX disclosed several critical vulnerabilities affecting its HTTP/2 module, including CVE-2026-123007, a 10-year-old flaw enabling remote code execution.
- Attackers can exploit these issues without authentication on servers with HTTP/2 enabled.
- The vulnerabilities impact major Ubuntu LTS versions from 16.04 through 26.10.
- F5 has released patched versions 1.31.9 and 1.30.7 to address the issues.
- Organizations should immediately update NGINX installations and review HTTP/2 configurations.
A set of critical vulnerabilities in NGINX's HTTP/2 implementation puts millions of web servers at risk of remote code execution and denial-of-service attacks. These flaws affect widely-used Ubuntu LTS versions and stem from improper handling of HTTP/2 connections and memory operations.
The most severe vulnerability, CVE-2026-123007, has existed in NGINX's codebase for over a decade, since version 1.9.5 released in September 2015. Dubbed "nginx2root," this flaw enables unauthenticated attackers to execute arbitrary code on vulnerable servers simply by sending specially crafted HTTP/2 requests.
Vulnerability Details
- CVE-2026-123007 ('nginx2root') is a 10-year-old flaw in NGINX's HTTP/2 implementation allowing remote code execution
- Additional vulnerabilities include CVE-2026-123633 (HTTP/2 connection reuse issues), CVE-2026-113425 (memory operation errors), and CVE-2026-123634 (name/address resolution problems)
- All vulnerabilities can be exploited remotely without authentication by sending malicious HTTP/2 requests
- Successful exploitation can lead to server compromise, data leakage, or complete denial of service
Affected Systems and Remediation
- Impacted Ubuntu versions include 16.04 LTS through 26.10, requiring immediate security updates via USN-9159-1
- NGINX versions prior to 1.31.9 and 1.30.7 contain the vulnerable code and must be upgraded immediately
- Servers with HTTP/2 enabled are at highest risk - administrators should disable HTTP/2 until patches are applied if immediate updates aren't possible
- F5 has published official patches and recommends reviewing HTTP/2 configurations even after updating
Sources
Sources
Security email updates
One digest email when we publish new security articles (TL;DR plus links to read more). Unsubscribe anytime from the message footer. See our Privacy Policy.