Xint has identified five vulnerabilities in nginx, codenamed NGINX2Root. The most critical vulnerability (CVE-2026-123007) allows for code execution with process privileges when the server receives requests using the HTTP/2 protocol. The other four issues also permit remote code execution but manifest under specific configurations or require certain conditions to be exploited. Additionally, researchers from Xint have discovered 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. Exploits have been prepared for all five vulnerabilities in nginx, which chain the exploitation of vulnerabilities in nginx and the Linux kernel for remote code execution with root privileges on a Linux server, even if nginx is running in a Docker container.
The issues have been fixed in nginx releases 1.30.7 and 1.31.9, which, in addition to the mentioned problems, have resolved five more vulnerabilities. The status of vulnerability remediation in distributions can be assessed on the following pages: Debian, Ubuntu, SUSE/openSUSE, RHEL, Gentoo, Arch, Fedora, FreeBSD, Rosa, ALT. As a workaround to mitigate the vulnerabilities, it's recommended to disable support for HTTP/2 and HTTP/3 protocols in nginx settings by placing 'http2 off;' and 'http3 off;' in each 'server' block and ensuring that the 'listen' directives do not include the 'http2' and 'quic' parameters, as well as removing configurations that lead to hostname resolution in DNS during request processing (for example, when using constructs like 'proxy_pass http://$host;' to forward connections to the backend).
Regarding the vulnerability in the Linux kernel, it leads to accessing already freed memory or double freeing of memory in the SCTP protocol implementation. The issue has been present since release 4.15 (January 2018) and remains unpatched. No CVE has been assigned. Details and exploits have not yet been publicly disclosed. To attack, it is sufficient to have the sctp kernel module present in the system (by default, it is included in many distributions and is automatically loaded 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'.
Identified issues in nginx:
- CVE-2026-123007 — integer overflow in the HTTP/2 flow control code, allowing for reading and writing data outside the allocated buffer. Reading from the area outside the buffer enables memory layout detection, while writing allows overwriting the cleanup function pointer, leading to the execution of arbitrary code with worker process privileges. It's sufficient to enable HTTP/2 request processing on server. The issue manifests starting with the release of nginx 1.9.5 (2015), when HTTP/2 support was introduced. Exploiting the vulnerability leaves no traces in standard access logs, but indirectly, attempts may be indicated by worker process crashes (segfault) in the error log and unusually high incoming traffic from a single IP.
- CVE-2026-123633 — use-after-free when handling HTTP/2 connections, occurring when an active connection is erroneously placed in the queue for release while the upstream module continues to work with it. The problem appears when specifying an insufficient number of connections through the worker_connections directive and using proxy_pass, fastcgi_pass, or grpc_pass directives in the configuration.
- CVE-2026-121810 — use-after-free in the HTTP/3 (QUIC) stream handling code, occurring when closing a QUIC connection while one of the HTTP/3 requests continues executing. The vulnerability manifests when proxying requests to the backend using proxy_pass, fastcgi_pass, or grpc_pass directives.
- CVE-2026-123634 — use-after-free in the DNS resolver code. The vulnerability appears in configurations with the resolver directive or when using mirror and proxy_pass directives with dynamic backend proxying by hostname (proxy_pass http://$host) in a scenario where both the main and mirrored requests await the same DNS response.
- CVE-2026-113425 — use-after-free in the mail proxy, manifesting when using the proxy on and auth_http settings in the mail block. The problem arises because the closing of the client connection frees the session, but the connection to the authentication service remains open, leading to accesses to already freed memory during its processing.
Other vulnerabilities fixed in nginx 1.30.7 and 1.31.9:
- CVE-2026-125283 — a buffer overflow occurring when using the "try_files" and "alias" directives simultaneously.
- CVE-2026-120967 — a vulnerability in the stream module that allows for the validation of client TLS certificates in the default context instead of the virtual host while synchronously completing TLS connection negotiations. server CVE-2026-120993 — null pointer dereference occurring when using the second version of the PROXY protocol in configurations with dynamically loaded TLS certificates. This issue may lead to a process crash.
- CVE-2026-123640 — bypassing restrictions in the ngx_stream_ssl_preread_module by sending specially crafted ClientHello TLS messages.
- CVE-2026-118899 — infinite looping in the process when reading the request body over SSL.
- Xint has identified five vulnerabilities in nginx, collectively codenamed NGINX2Root.
Source: opennet.ru
