Cybersecurity Research

Five nginx flaws and an unpatched Linux kernel bug can combine to give attackers root

Hacktron · 19 Nov 2026
Key Takeaway Update nginx to 1.30.7 or 1.31.9 (or your distribution's patched package) and disable HTTP/2 where you cannot patch straight away.

Xint has named five nginx vulnerabilities, plus a separate Linux kernel flaw, "nginx2root". Each nginx bug can lead to code execution as the nginx worker process, but only under a specific configuration. The most prominent, CVE-2026-123007, affects unpatched nginx builds with HTTP/2 enabled and has been present since 2015. Fixes shipped on 18 November 2026 in nginx 1.31.9 (mainline) and 1.30.7 (stable). Distributions may backport fixes without changing the version number, so the full package version should be checked against the distribution's advisory.

Xint chained CVE-2026-123007 with the kernel flaw to reach root, including from inside a Docker container where SCTP was reachable. The kernel bug is a use-after-free in SCTP, present since Linux 4.15, and had no CVE or kernel patch at the time of disclosure. Whether it is reachable depends on the kernel, its modules and any container restrictions. The other four nginx bugs are use-after-free issues in HTTP/2 and HTTP/3 connection handling, DNS resolution during subrequests, and the mail proxy's authentication.

CVE-2026-123007 is an integer underflow in HTTP/2 flow control that can lead to a heap read and write. F5 says code execution needs ASLR disabled or bypassed. Rapid7 has published a proof of concept that achieved code execution on a fresh nginx 1.31.8 container by sending about 128 GB of HTTP/2 data. Rapid7 expects it to fail on slower links, busy servers or behind a proxy, though those are limits of the exploit, not the bug. Xint has withheld its own exploits.

watchTowr reported no exploitation in the wild as of 18 November, and as of 20 November none of the CVEs was in CISA's Known Exploited Vulnerabilities catalog. F5 says BIG-IP, BIG-IQ and F5OS are not affected.

Why it matters

Many teams treat a web server compromise as contained to a low-privilege worker, especially inside containers. This chain breaks that assumption: with an unpatched kernel bug, nginx code execution can become root on the host. Because the kernel flaw had no patch at disclosure, nginx patching alone does not close the whole path, so teams must also decide whether to block SCTP.

What to do

  • Upgrade nginx to 1.30.7 or 1.31.9, or confirm your distribution's backport covers CVE-2026-123007.
  • Disable HTTP/2 on affected ports if you cannot patch yet.
  • Add install sctp /bin/false to a .conf file in /etc/modprobe.d/ on hosts that do not use SCTP.
  • Restart nginx if workers still show worker process is shutting down after a reload.

Summarised by CISO AI from Hacktron, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.