# Critical NGINX Vulnerabilities Expose Servers to Remote Code Execution

*Published November 20, 2026*
*Source: [https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html](https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html)*
*Official advisory: [BSI 2026-306805-1032](https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2026/2026-306805-1032_bits.html)*

## Executive Summary

Critical vulnerabilities in NGINX's HTTP/2 support allow unauthenticated remote code execution on affected servers, prompting the release of patches. While no real-world attacks have been reported, users should upgrade promptly and implement mitigations to safeguard their systems.

*This is a Premium edition: its actionable insights are available to sec-news.ai Premium members —*
*[read the story](https://www.sec-news.ai/news/critical-nginx-vulnerabilities-expose-servers-to-remote-code-execution) or [see plans](https://www.sec-news.ai/pricing).*

## Article

A significant security flaw in NGINX's HTTP/2 support, known as 'nginx2root', has been discovered, allowing unauthenticated remote code execution on vulnerable servers. This flaw, identified as CVE-2026-123007, has been part of NGINX's open-source code since version 1.9.5, which was released in September 2015. Affected versions include all releases from 1.9.5 to 1.31.8, with fixed versions 1.31.9 and 1.30.7 being released recently. These vulnerabilities enable attackers to execute code where Address Space Layout Randomization (ASLR) is disabled or bypassed. Researchers from Wiz and Xint have successfully demonstrated the execution of code through this flaw. In particular, Xint's tests showed that code could gain root access on the host via another bug in the Linux kernel's SCTP code, even when NGINX was running inside a Docker container. 

No real-world attacks exploiting these vulnerabilities have been reported so far. However, proof-of-concept code is available on GitHub, indicating potential exposure. The vulnerabilities affect both open-source NGINX and NGINX Plus in specific releases. F5, the company behind NGINX, has released patches that fix the vulnerabilities. Users are advised to upgrade to the latest versions and restart NGINX to ensure the updates take effect. Temporary mitigations include disabling HTTP/2 to block some of the vulnerabilities and securing the network environment to limit exposure. Security teams are encouraged to monitor their systems for unusual behavior that could indicate exploitation attempts, such as unexpected program starts by NGINX workers or unusual outbound connections. 

Until the Linux kernel SCTP bug is addressed, it is recommended to block the SCTP kernel module from loading on systems not using this protocol. Security teams should take immediate action to apply patches, verify configurations, and monitor for any indicators of compromise.
