NGINX2Root – Critical NGINX and Linux Kernel Vulnerabilities
Daniel Nashed – 18 November 2026 19:46:14
November 18, 2026
Security researchers at Xint have disclosed NGINX2Root, a collection of five critical NGINX vulnerabilities that can allow unauthenticated remote code execution.
The most significant vulnerability, CVE-2026-123007, affects NGINX servers with HTTP/2 enabled. It has existed since HTTP/2 support was introduced in 2015.
However, not all five vulnerabilities require HTTP/2. Other affected configurations include HTTP/3, specific reverse proxy setups, and the NGINX mail proxy.
The Linux Kernel and Docker Risk
The researchers also discovered a separate vulnerability in the Linux kernel's SCTP implementation, introduced in Linux 4.15 in 2018.
It's not a module needed in by most customers, but it is installed and available for load by default.
By combining the NGINX vulnerability with this kernel issue, they demonstrated:
- Remote code execution in NGINX.
- Privilege escalation to root.
- Escape from a Docker container to the underlying Linux host.
This is particularly concerning because all Docker containers share the host kernel.
Until a kernel fix is available, systems that do not require SCTP can prevent normal module autoloading with:
echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf
Simply checking that the SCTP module is not currently loaded is insufficient because Linux may load it automatically when requested.
Updates and Our Response
NGINX 1.31.9 contains the fixes for the five NGINX vulnerabilities. Linux distributions may also provide backported fixes.
I have already rebuilt our NGINX Docker NRPC container image with version 1.31.9, although none of our supplied configurations enables HTTP/2 out of the box.
And I also reviewed our Linux hosts and disabled SCTP module loading where it is not required.
I recommend checking NGINX installations, including those bundled in Docker images and third-party products, and reviewing the underlying Linux kernel exposure.
There is no kernel patch yet. But the only known way to leverage the issue is the broken NGINX HTTP/2 implementation.
Further reading:
Xint Security – NGINX2Root Technical Disclosure --> https://xint.io/blog/nginx2root-remote-code-execution
- Comments [0]