← Back to news 19.11.2026

nginx2root: disabling HTTP/2 closes two of five holes

On 18 November, nginx released versions 1.31.9 and 1.30.7. Among other things, they close five vulnerabilities that the security firm Xint describes as nginx2root: each is said to lead to code execution on its own, the most severe without authentication as soon as HTTP/2 is active. Why disabling HTTP/2 covers only two of them, why the version number says little for distribution packages, and why a reload is not enough.

On 18 November 2026, the nginx project released versions 1.31.9 (mainline) and 1.30.7 (stable). The change list for 1.31.9 names ten security fixes. Five of them were found by the security firm Xint and described under the name nginx2root, with its own website and technical analysis.

What Xint describes

According to Xint, each of the five vulnerabilities leads to code execution on its own, depending on the configuration:

  • CVE-2026-123007: HTTP/2 is enabled. That is enough. According to Xint, an unauthenticated attacker can execute commands with the privileges of the nginx worker process. The flaw has been in every official release from nginx 1.9.5, when HTTP/2 was introduced in 2015, up to 1.31.8.
  • CVE-2026-123633: HTTP/2 with requests forwarded to a backend.
  • CVE-2026-121810: HTTP/3 with requests forwarded to a backend.
  • CVE-2026-123634: the resolver is used, the proxy_pass destination depends on the request, and mirror is involved.
  • CVE-2026-113425: nginx as a mail proxy with auth_http. The flaw is triggered during login, and the attacker needs no valid credentials.

On top of that comes a sixth vulnerability, not in nginx but in the SCTP part of the Linux kernel. With it, Xint got from the nginx worker to root on the host, in one test also out of a Docker container. No kernel fix was available at the time of publication. Xint recommends blocking the module from loading on hosts that do not use SCTP.

The nginx project itself rates the vulnerabilities in its advisories as "major" or "medium" and phrases it more cautiously: a worker process crash is possible, "or might have potential other impact". The assessment of exploitability comes from Xint.

Three things that easily go wrong when patching

  • Disabling HTTP/2 is not enough. It is the obvious immediate measure, and according to Xint it blocks CVE-2026-123007 and CVE-2026-123633. The other three paths remain open. For HTTP/3, mail proxy and resolver, Xint describes separate mitigations: remove QUIC listeners, let the mail proxy listen only locally, switch proxy_pass to a fixed upstream group.
  • The version number misleads. Ubuntu 24.04 ships nginx 1.24.0, Ubuntu 22.04 1.18.0, Debian 12 1.22.1. Distributions often backport fixes without changing the version number. Whether a server is patched is then only shown by the full package version compared with the distribution's security advisory. Red Hat and SUSE publish these advisories in machine-readable CSAF format, see our directory of CSAF sources.
  • A reload is not an update. Xint points this out explicitly: after installation, nginx must be restarted or a supported binary upgrade performed. Reloading the configuration does not replace the running program.

What to do

  • Establish the inventory. Where does nginx run, including as a reverse proxy in front of business applications, in containers and on appliances? In which version, from which package?
  • Update, then restart. To 1.31.9 or 1.30.7, for distribution packages to the level in the security advisory.
  • Until then, the matching mitigation. Depending on configuration HTTP/2, HTTP/3, mail proxy or resolver, not just HTTP/2.
  • Block SCTP where it is not needed. As long as the kernel is not fixed.
  • Do not only look at the access log. According to Xint, an attack via CVE-2026-123007 leaves few traces there. Unusual worker crashes and processes started by workers are better indicators.

The test question

Do you know, for every nginx on your network, which full package version is running, and whether it was restarted after the update?

Sources

nginx security advisories and nginx CHANGES (changes in 1.31.9 of 18 Nov 2026), retrieved 18 November 2026.

Xint, NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching, with configuration table, check commands and mitigations, and nginx2root.com.

Matching solution isidaten for ISO/IEC 27001

Questions about this update?

Talk to us – we are happy to show you this feature in a demo.