NGINX2Root – Vulnerabilities In Nginx That Allow Code Execution When Using HTTP/2 Or HTTP/3

Xint has identified five vulnerabilities in nginx, codenamed NGINX2Root. The most dangerous vulnerability (CVE-2026-123007) allows code to be executed with workflow rights when receiving requests on the server using the HTTP/2 protocol. The remaining 4 problems also allow remote code execution, but appear in the presence of specific settings or require special conditions for operation. In addition, researchers from Xint have identified a new vulnerability in the SCTP subsystem of the Linux kernel, which allows a local user to gain root privileges on the system and bypass container isolation. For all 5 vulnerabilities in nginx, exploits have been prepared that exploit vulnerabilities in nginx and the Linux kernel in a chain for remote code execution with root rights on a Linux server, even if nginx is running in a Docker container.

The problems have been fixed in the releases nginx 1.30.7 and 1.31.9, in which, in addition to the noted problems, 5 more vulnerabilities were fixed. The status of vulnerabilities in distributions can be assessed on these pages: Debian, Ubuntu, SUSE/openSUSE, RHEL, Gentoo, Arch, Fedora, FreeBSD, Rosa, ALT. As a workaround to block vulnerabilities, it is recommended to disable support for the HTTP/2 and HTTP/3 protocols in the nginx settings by setting “http2 off;” and “http3 off;” in each “server” block and making sure that the “listen” directives do not contain the “http2” and “quic” parameters, and also remove settings that lead to resolving host names in DNS during request processing (for example, when using constructs like “proxy_pass https://$host;” to forward connections to the backend).

As for the vulnerability in the Linux kernel, it leads to access to already freed memory or double freeing memory in the implementation of the SCTP protocol. The problem has been appearing since release 4.15 (January 2018) and remains unfixed. No CVE assigned. The details and exploit have not yet been publicly disclosed. For an attack, it is enough to have the sctp kernel module in the system (present by default in many distributions and loaded automatically when an SCTP socket is opened). To block the loading of the sctp module, it is recommended to create a configuration file /etc/modprobe.d/sctp.conf containing “install sctp /bin/false”.

/Reports, release notes, official announcements.