Skip to content

Image: cdn.prod.website-files.com · rights & removal

Executive Summary

Vulnerabilities in NGINX, collectively referred to as NGINX2Root, involve five memory-safety bugs discovered on November 18, 2026, which allow an unauthenticated remote attacker to corrupt memory in an NGINX worker process. These bugs carry CVSS scores ranging from 8.1 (High) to 9.2 (Critical). The fixes are available in NGINX versions 1.31.9 (mainline) and 1.30.7 (stable), with corresponding fixes for NGINX Plus. The chain of exploitation also involves a separate Linux kernel bug in the Stream Control Transmission Protocol (SCTP) code, which allows for achieving root access on the host. While no public proof-of-concept or in-the-wild exploitation has been reported, researchers have developed exploits that bypass ASLR. The vulnerability's reach is significant, affecting many systems, especially those using HTTP/2, and the kernel bug exacerbates the impact by enabling container escapes from NGINX worker compromises.

Facts Only

* Five memory-safety bugs were published for NGINX on November 18, 2026.
* All five CVE records received CVSS 3.1 scores of 8.1 and CVSS 4.0 scores of 9.2.
* Fixes were shipped in NGINX 1.31.9 (mainline) and 1.30.7 (stable).
* The vulnerabilities are network-based and do not require authentication.
* Impact includes worker crashes, memory corruption, and code execution with ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds over HTTP/2 with TLS on 64-bit systems.
* A separate Linux kernel bug in SCTP code allows for use-after-free and double-free, enabling an attacker to call arbitrary kernel functions.
* The kernel bug has no assigned CVE or released fix.
* Exposure depends on the specific NGINX version and distribution package status.
* Exploitation requires specific features to be enabled; bugs are contingent on HTTP/2 support for the most widely reachable vulnerability.
* A compromise of an NGINX worker can lead to root on the host, including container escape, via the kernel bug.

Full Take

The narrative centers on a critical gap between upstream fixes and real-world deployment practices, specifically highlighting how patching processes introduce systemic risk in software supply chains. The primary tension is between the rapid release of patches and the slow adoption by operating environments like distribution packages and container images, creating an exploitable window where theoretical fixes do not translate into actual security for deployed assets. The complexity increases because a single vulnerability chain—the NGINX bugs combined with the kernel flaw—transforms an unprivileged service compromise into host-level root access. This forces defenders to move beyond simple patch management to understand runtime execution and configuration posture, as static version checks alone are insufficient. The implications point toward a failure in automated verification of security state across heterogeneous environments (hosts vs. containers). The focus shifts from merely patching software versions to managing the entire operational context—ensuring configurations are restrictive, hardening the kernel interaction surface, and implementing runtime detection that monitors post-exploitation behavior rather than just known signatures. How do organizations reconcile the time lag between upstream fixes and fleet deployment with the immediate threat posed by complex privilege escalation chains?

From the original · Sysdig Blog

Get security briefings from the Threat Research Team New campaigns, attacker techniques, and detection guidance — straight to your inbox. Falco Feeds extends the power of Falco by giving open source-focused companies access to expert-written rules that are continuously updated as new threats are discovered.
Read the full story at webflow.sysdig.com

Sentinel unavailable

The automated check of the source article's wording did not complete, so no result is shown.

This looks only at the wording of the original source article, not at this page's AI-written sections. A small local AI model made this estimate. It has not been checked against known human and machine texts, so treat it as provisional. It cannot show who wrote an article.

NGINX2Root: Five RCE bugs in NGINX, a Linux kernel path to root, and how to detect exploitation | Huntaegis