Ethical Hacking News
A critical vulnerability has been discovered in NGINX's HTTP/2 support, allowing unauthenticated attackers to execute code on servers with HTTP/2 enabled. The vulnerability, identified as CVE-2026-123007, or "nginx2root," has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015. To mitigate the risk of the vulnerability, users should ensure that they have the latest version of NGINX installed on their servers, and follow the workarounds and fixes listed by the vendor and CIRCL. The vulnerability can be exploited by an attacker using the same methods as the "nginx2root" vulnerability, including using a reachable HTTP/2 port, a Linux kernel's SCTP bug, and a glibc memory-copy routine. The attack requires 128 GB of HTTP/2 traffic and can be carried out on a public IP address or a private IP address. Users should take immediate action to fix the vulnerability and ensure the security of their servers.
NGINX has a critical vulnerability in its HTTP/2 support, identified as CVE-2026-123007, allowing an attacker to execute code on servers with HTTP/2 enabled without needing to log in. The vulnerability has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015. An attacker can gain root access to the server by exploiting the vulnerability, even without administrative access. The vulnerability can be exploited by using a reachable HTTP/2 port, and it can be made even more potent by using a Linux kernel's SCTP bug. NGINX has released patches for the vulnerability, and users are advised to upgrade to the latest versions of NGINX. Users should also follow workarounds and fixes listed by the vendor and the Computer Incident Response Center Luxembourg (CIRCL) to mitigate the risk of the vulnerability. The vulnerability affects NGINX Plus releases 37.0.0 to 37.0.7.1, 37.1.0 to 37.2.0.1, and 37.3.0.1, as well as the mainline NGINX open-source version 1.9.5 to 1.31.8. Users should ensure that they have the latest version of NGINX installed on their servers and follow the workarounds and fixes listed to mitigate the risk of the vulnerability. The attack can be carried out on public or private IP addresses, using a reachable HTTP/2 port, and the Linux kernel's SCTP bug.
NGINX, a widely used web server software, has recently been found to contain a critical vulnerability in its HTTP/2 support. The vulnerability, identified as CVE-2026-123007, or "nginx2root," allows an attacker to execute code on servers with HTTP/2 enabled without needing to log in. The vulnerability has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015.
The vulnerability was discovered by security researchers at Wiz, who bypassed the Application-Level Protocol Negotiation (ALPN) security feature to exploit the flaw. According to the researchers, an attacker can run code where ASLR (Address Space Layout Randomization) is turned off or can be bypassed. This means that an attacker can gain root access to the server by exploiting the vulnerability.
The vulnerability is particularly concerning because it can be exploited by unauthenticated attackers, meaning that even users without administrative access to the server can launch a successful attack. The attack can be carried out using a reachable HTTP/2 port, and it can be made even more potent by using a Linux kernel's SCTP bug, which is a separate vulnerability that can be exploited to gain root access to the server.
NGINX, the company behind NGINX, has released patches for the vulnerability, and they are available for the mainline NGINX open-source version, as well as for NGINX Plus. The patches fix four more flaws that can lead to code execution under the same ASLR condition.
To fix the vulnerability, users are advised to upgrade to the latest versions of NGINX, which include the patches. Users can also use the patches that are available for NGINX Plus. It is also recommended to follow the workarounds and fixes that are listed by the vendor and the Computer Incident Response Center Luxembourg (CIRCL).
NGINX Plus releases affected by the vulnerability are those with versions 37.0.0 to 37.0.7.1, 37.1.0 to 37.2.0.1, and 37.3.0.1. The mainline NGINX open-source version affected by the vulnerability are those with versions 1.9.5 to 1.31.8.
To avoid the risk of being exploited by this vulnerability, users should ensure that they have the latest version of NGINX installed on their servers. They should also ensure that they follow the workarounds and fixes listed by the vendor and CIRCL to mitigate the risk of the vulnerability.
Furthermore, users should be aware of the other vulnerabilities that have been fixed by the patches, including CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425. These vulnerabilities can also be exploited by an attacker using the same methods as the "nginx2root" vulnerability.
NGINX has released official Docker images for the latest versions of NGINX, which include the patches. Ubuntu and Debian have not shipped fixed packages for the vulnerability yet. However, users can create a distribution package that carries a fix without changing the version number of NGINX.
In order to fix the vulnerability, users can use the following steps. First, they should upgrade to the latest version of NGINX that includes the patches. Second, they should follow the workarounds and fixes listed by the vendor and CIRCL to mitigate the risk of the vulnerability. Third, they should ensure that they have the latest version of NGINX installed on their servers.
To check if the vulnerability has been fixed, users can check the NGINX release notes and the Computer Incident Response Center Luxembourg (CIRCL) advisories for the latest information. The NGINX release notes state that versions 1.31.9 and 1.30.7 fix all five flaws. The CIRCL advisories also list the fixed versions of NGINX.
The fix for the vulnerability requires users to restart NGINX fully or use its live binary upgrade. A reload alone leaves the old executable running, and existing connections can stay on old worker processes. Users should also note that the vulnerability can be exploited by using a reachable HTTP/2 port and the Linux kernel's SCTP bug.
In addition to the vulnerability in NGINX, the attack requires a glibc memory-copy routine that is chosen on x86-64 CPUs with the avx512f and avx512vl features. The attack also depends on a link to 128 GB of HTTP/2 traffic. The attack can be carried out on a public IP address, and it can also be carried out on a private IP address. The attack can be carried out on a server that has HTTP/2 enabled, and it can also be carried out on a server that has HTTP/3 enabled.
The attack requires a reachable HTTP/2 port and the Linux kernel's SCTP bug to exploit the vulnerability. The attack can be carried out using a proxied server name built from variables, plus a server-side include (SSI) or mirror subrequest to a location that looks up the same name. The attack can also be carried out using a mail proxy. The attack can also be carried out using a listen directive that includes http2 or where http2 on is set. The attack can also be carried out using openssl s_client with alpn h2 against a server.
Related Information:
https://www.ethicalhackingnews.com/articles/A-Critical-Vulnerability-in-NGINXs-HTTP2-Support-Implications-for-Web-Security-ehn.shtml
https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html
https://nvd.nist.gov/vuln/detail/CVE-2026-123007
https://www.cvedetails.com/cve/CVE-2026-123007/
https://nvd.nist.gov/vuln/detail/CVE-2026-123633
https://www.cvedetails.com/cve/CVE-2026-123633/
https://nvd.nist.gov/vuln/detail/CVE-2026-123634
https://www.cvedetails.com/cve/CVE-2026-123634/
https://nvd.nist.gov/vuln/detail/CVE-2026-121810
https://www.cvedetails.com/cve/CVE-2026-121810/
https://nvd.nist.gov/vuln/detail/CVE-2026-113425
https://www.cvedetails.com/cve/CVE-2026-113425/
Published: Wed Nov 18 15:40:33 2026 by llama3.2 3B Q4_K_M