Five of the nginx flaws fixed on November 18 can let an attacker run code with the privileges of an nginx worker process. Xint, which reported all 5, took the next step with a separate bug in the Linux kernel’s SCTP code: in its tests, an attacker running code as the worker could reliably gain root, even from inside a Docker container. When Xint disclosed the chain, no kernel fix was available.

The 5 flaws, which Xint calls NGINX2Root, carry a CVSS 4.0 score of 9.2 in their CVE records, while nginx.org rates 2 of them major and 3 medium. The fixes are in nginx 1.31.9 (mainline), which addresses 10 vulnerabilities including these 5, and 1.30.7 (stable), which addresses 9, as the tenth affects only the mainline branch. After this release, the nginx.org advisories page lists 36 vulnerabilities with 2026 identifiers, against 2 from 2025.

Which Configurations Each Flaw Needs

CVEAffected configurationVulnerable since (nginx.org)Blocked by turning off HTTP/2
CVE-2026-123007HTTP/2 enabled1.9.5Yes
CVE-2026-123633HTTP/2 with requests forwarded to a backend, when worker_connections run short1.19.7Yes
CVE-2026-121810HTTP/3 with requests forwarded to a backend, when worker_connections run short1.25.0No
CVE-2026-123634proxy_pass with a variable hostname and resolver, while subrequests such as mirror or SSI resolve the same name0.6.18No
CVE-2026-113425Mail proxy with proxy on and auth_http0.5.33No

Several teams reported the 2 HTTP/2 flaws independently. Rapid7 published a proof of concept for CVE-2026-123007. Its technique needs about 128 GB of HTTP/2 traffic, and it relies on a glibc memory-copy routine that x86-64 systems select when the processor supports certain AVX-512 features. On a connection slower than roughly 300 Mbit/s, the attack runs past nginx’s default 1-hour connection lifetime and fails. Wiz demonstrated code execution on nginx serving ordinary static files and has not released its exploit.

Rapid7 adds that a proxy in front of nginx will likely not pass the attacker’s frames through in a usable form. Cloudflare reaches the same conclusion for its HTTP proxy: client connections end at its edge, so origins behind it are shielded from the HTTP/2 and HTTP/3 attacks, provided they cannot be reached directly. As of November 19, Cloudflare reported that none of the 5 CVEs was in CISA’s Known Exploited Vulnerabilities catalog and that it had seen no reports of exploitation in the wild.

Plesk Enables HTTP/2 by Default, cPanel’s nginx Does Not

Plesk ships nginx in two roles: as the web server for websites (sw-nginx) and for the Plesk interface (sw-cp-server). Its advisory lists both as affected up to nginx 1.30.6, Plesk Obsidian 18.0.82 Update 3 and 18.0.81 Update 8. Plesk’s documentation states that HTTP/2 is enabled by default for websites with SSL/TLS. The fix, nginx 1.30.7, arrived for both components in 18.0.82 Update 4 and 18.0.81 Update 9, released on November 19.

For servers not yet updated, the advisory describes a mitigation that turns off HTTP/2 and HTTP/3 for websites, with separate steps for the panel on port 8443. Directives set in custom configuration, including resolver and mirror, have to be removed by hand. Once the update is installed, Plesk asks admins to turn HTTP/2 back on and restore the removed directives.

In cPanel, ea-nginx gets HTTP/2 from an add-on package, ea-nginx-http2. None of the 19 EasyApache 4 profiles in cPanel’s public repository includes it, not even the default nginx profile. cPanel shipped ea-nginx 1.31.9 in EasyApache 4 25.98 on November 19.

HTTP/3, which CVE-2026-121810 requires, has to be turned on manually in Plesk, and cPanel does not compile it into ea-nginx.

The two panels also ship different nginx versions. The 1.30.7 release in Plesk contains only security changes. The 1.31.9 release that cPanel ships also rejects header lines without a colon, in requests and in upstream responses, and stops a worker process on initgroups() failures other than EPERM. The nginx blog lists both as changes that can break a working setup.

The Kernel Step and the SCTP Stopgap

Updating nginx closes the entry point, not the kernel bug. Xint describes it as a use-after-free in the kernel’s SCTP implementation, present since 2018. On many Linux distributions the SCTP module is installed by default and loads automatically when a program opens an SCTP socket. Until a kernel fix is available, Xint advises hosts that do not use SCTP to block the module with a line in a file under /etc/modprobe.d/: install sctp /bin/false. The rule does not unload a module that is already loaded and does not cover SCTP compiled into the kernel.

Xint also notes that a configuration reload does not replace the running binary, so nginx needs a restart after the update. Linux distributions often backport fixes without changing the version reported by nginx -v, so the full package version has to be checked against the distribution’s advisory.