10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers
Overview
A significant vulnerability has been discovered in NGINX's HTTP/2 support, allowing unauthenticated attackers to execute code on servers with HTTP/2 enabled. This flaw, identified as CVE-2026-123007 and nicknamed 'nginx2root,' has existed in the open-source software since version 1.9.5, which was released in 2015. The issue poses a serious risk as it enables attackers to gain control of servers without any login credentials. In response, F5, the company that oversees NGINX, has released patches in versions 1.31.9 and 1.30.7 to address the vulnerability. Users of NGINX are strongly advised to update their systems promptly to mitigate the risks associated with this long-standing flaw.
Key Takeaways
- Affected Systems: NGINX versions 1.9.5 and later with HTTP/2 enabled; specifically, versions 1.31.9 and 1.30.7 are the patched versions.
- Action Required: Upgrade to NGINX versions 1.
- Timeline: Ongoing since September 2015
Original Article Summary
A flaw in NGINX's HTTP/2 support can allow an attacker to run code on servers with HTTP/2 enabled, without needing to log in. The decade-old flaw, CVE-2026-123007, dubbed "nginx2root," has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015. Fixed versions 1.31.9 and 1.30.7 came out today. F5, the company behind NGINX, says attackers can run code where
Impact
NGINX versions 1.9.5 and later with HTTP/2 enabled; specifically, versions 1.31.9 and 1.30.7 are the patched versions.
Exploitation Status
No active exploitation has been reported at this time. However, organizations should still apply patches promptly as proof-of-concept code may exist.
Timeline
Ongoing since September 2015
Remediation
Upgrade to NGINX versions 1.31.9 or 1.30.7 to patch the vulnerability.
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.
Related Topics: This incident relates to CVE, Vulnerability, Update, and 2 more.