nginx administrators have patches to deploy: versions 1.31.9 and 1.30.7 fix five vulnerabilities that Xint says each enable unauthenticated remote code execution in different configurations. Xint’s NGINX2Root disclosure also includes a separate Linux kernel flaw that the researchers chained with nginx exploitation to obtain root privileges on the host in tests. Source Source
Disabling HTTP/2 blocks two of the five nginx attack paths, not the other three. It’s a useful stopgap, not permission to put patching back in the queue. Source Source
Static-file servers don’t get a pass
The broadest concern is CVE-2026-123007, a memory-corruption flaw in HTTP/2 flow control whose code history dates to nginx 1.9.5 in 2015. Exposure requires an unpatched build with HTTP/2 support and an affected listener accepting HTTP/2 connections. An old-looking version number alone doesn’t establish vulnerability. Source Source
Wiz says it independently demonstrated remote code execution through this flaw on a server serving ordinary static files, without a backend application or third-party module. Its tested path used HTTP/2 over TLS on 64-bit systems. A plain folder of files is not a security exemption. Source
The second HTTP/2 flaw, CVE-2026-123633, involves reverse-proxy processing when available connection slots run low. Memory is freed while request processing still needs it—a use-after-free that Wiz and Xint say they turned into code execution. Source Source
Five flaws, different configurations
The five nginx vulnerabilities are independent attack paths; an attacker does not need to combine all five. Source
Xint warns that other features creating subrequests may also reach the resolver bug, so disabling mirroring alone does not establish safety. Source
Patch the running service, not just the package
The official nginx advisory index lists 1.31.9 and 1.30.7 as fixed releases for each of the five issues. Administrators should install the appropriate fixed upstream release or a vendor package containing the fixes. Source Source
- Check the full package version against the vendor advisory. Distributions can backport fixes without changing the upstream version shown by
nginx -v. Packages, appliances and container images need their own patch-status checks. Source Source
- Replace the running binary. Xint recommends the restart, rolling replacement or supported binary-upgrade procedure appropriate to the deployment, then verifying that old processes have exited.
nginx -s reload reloads configuration; it does not load the newly installed executable. Source
- Test application compatibility before temporarily disabling HTTP/2. Existing HTTP/2 connections must end before that mitigation fully takes effect. Services such as native gRPC require HTTP/2 and can stop working when it is disabled. DNS-resolver, HTTP/3 and mail-proxy exposure still need separate attention. Source Source
Root access takes a separate step
The nginx vulnerabilities initially provide the privileges of the worker process handling the request—not automatic root access. Xint says it chained nginx exploitation with a separate flaw in the Linux kernel’s SCTP networking subsystem to reach host root in tests, including a setup with nginx running inside a Docker container. Whether SCTP is reachable depends on the kernel, available modules and container restrictions. Source
Xint said a kernel fix was still pending at publication. It recommends blocking SCTP module loading on hosts that don’t need it, but warns that this neither unloads an already-loaded module nor disables SCTP compiled into the kernel. Updating nginx closes the nginx entry paths; it does not repair that separate kernel flaw. Source Source
Xint says it had no evidence of exploitation as of publication, while acknowledging that it could not rule it out. Administrators investigating possible compromise should review unexpected programs launched by nginx workers, crashes and unusual network activity, without treating those signs as proof on their own. Ordinary access logs do not fully record the HTTP/2 control frames involved. A quiet access log is not a clean bill of health. Source Source Source
Comments