JM Tech Power

新闻

NGINX2Root: update nginx to 1.30.7 or 1.31.9, or install your Linux distribution's fix

← 全部文章 邮箱 RSS Atom

News · written 22 November 2026. A summary for readers, not technical advice — check the sources at the end for the details.

On 18 November 2026 the nginx project released 1.30.7 (stable) and 1.31.9 (mainline). They fix nine and ten security issues. The same day the research company Xint published five of them under the name NGINX2Root, together with a separate Linux kernel bug. If you run nginx, update it.

The five bugs, and who is exposed

  • CVE-2026-123007: HTTP/2 is enabled. In nginx since 1.9.5, released in 2015.
  • CVE-2026-123633: HTTP/2, with requests passed to a backend.
  • CVE-2026-121810: HTTP/3, with requests passed to a backend.
  • CVE-2026-123634: resolver is used and subrequests look up the same name, for example with mirror.
  • CVE-2026-113425: nginx is used as a mail proxy.

How serious is it?

The first bug affects the most servers. Xint says it ran commands as the nginx worker without signing in, then used the kernel bug, which is in SCTP, to become root on the host, also from inside a Docker container.

F5, which maintains nginx, is more cautious: the bug can crash a worker, and code can run where address randomisation (ASLR) is off or can be bypassed. F5 scores it 9.2 (Critical) on CVSS 4.0 and 8.1 (High) on CVSS 3.1. CISA recorded no known exploitation in its assessment of 19 November, and the bug was not in its Known Exploited Vulnerabilities list of 20 November.

Check your server

See which version you have, and whether HTTP/2 is switched on:

nginx -v
sudo nginx -T 2>&1 | grep -n http2

In the second result, look for http2 on; or a listen line with http2. Do not judge by the version alone: Linux distributions copy fixes into older versions, so compare the full package version.

Packages with the fix for CVE-2026-123007

  • nginx.org: 1.30.7 or 1.31.9.
  • Ubuntu 22.04: 1.18.0-6ubuntu14.23.
  • Ubuntu 24.04: 1.24.0-2ubuntu7.20.
  • Ubuntu 26.04: 1.28.3-2ubuntu1.13.
  • Ubuntu 26.10: 1.30.4-7ubuntu1.2.
  • Debian 12: 1.22.1-9+deb12u11.
  • Debian 13: 1.26.3-3+deb13u11.
  • Red Hat Enterprise Linux 8, 9 and 10: updates dated 20 November. See Red Hat's page for your exact stream.

On Debian or Ubuntu:

sudo apt update
sudo apt install --only-upgrade nginx
dpkg -s nginx | grep Version
sudo systemctl restart nginx

Restart after updating: Xint notes that a reload does not replace the running program. If nginx came from a control panel, a Docker image or another bundle, the system's package update may not touch it, so look for that supplier's update.

If you cannot update today

  • Turn off HTTP/2 on every affected port: http2 off; on 1.25.1 and later, and remove http2 from listen lines. This covers only two of the five bugs, and services that need HTTP/2, such as gRPC, will stop working.
  • Turn off HTTP/3 if you use it, and limit who can reach a mail proxy.
  • For the resolver bug, see the workaround in Xint's report.
  • Run sudo nginx -t, then restart, so that old connections do not keep the old settings.

The kernel bug is separate

Updating nginx does not fix the SCTP bug. No kernel patch was available when Xint and LWN wrote on 18 November. Until your distribution ships one, Xint suggests that hosts which do not use SCTP put install sctp /bin/false in a .conf file in /etc/modprobe.d/. That does not unload a module that is already running: check with lsmod | grep sctp.

Sources

More news at https://jmtechpower.com/articles.

评论 (0)

暂无评论,成为第一个评论者!