Thursday 19 November 2026 · Breaking news SearchSign inSubscribe
Best Effort

The weekday briefing on Australian telecommunications, data centres and AI infrastructure.

Breaking news · World

F5 patches five critical NGINX flaws, one chainable with a Linux kernel bug to root

F5 released fixes on 18 November 2026 for five critical NGINX vulnerabilities, each rated 9.2 under CVSS 4.0. Xint, which grouped them as NGINX2Root, chained the most serious with an unpatched Linux kernel SCTP bug to take root on the host.

F5 published security advisories on 18 November 2026 for five critical vulnerabilities in NGINX Open Source and NGINX Plus, all scored 9.2 under CVSS 4.0. Security firm Xint collectively named them NGINX2Root and said each has a proven exploit. Fixed open-source versions are 1.31.9 (mainline) and 1.30.7 (stable).

The most serious is CVE-2026-123007, an integer underflow in HTTP/2 flow control that lets an unauthenticated attacker run code on a server. Every official open-source release from 1.9.5 through 1.31.8 is affected, according to NGINX's advisories; 1.9.5 was released on 22 September 2015. NGINX Plus is also affected, in 37.x releases before the fixed builds and in R34 to R36, according to the vendor advisory. F5 lists no fix for NGINX Plus R34 to R36.

The second HTTP/2 flaw, CVE-2026-123633, is a use-after-free affecting HTTP/2 connections proxied to a backend. The other three need specific configurations: CVE-2026-123634 in the resolver, CVE-2026-121810 in HTTP/3 setups and CVE-2026-113425 in the mail proxy. F5 said code execution requires ASLR to be disabled or bypassed, while Wiz Research reported that the two HTTP/2 bugs can be used to bypass it.

On its own, CVE-2026-123007 gives an attacker only the privileges of an NGINX worker process. Xint escalated to root using a Linux kernel bug in SCTP handling that dates back to Linux 4.15, released in 2018, including from inside a Docker container. At disclosure that kernel flaw had neither a CVE identifier nor a patch, and Xint held back most of the details until a fix exists. Xint recommended blocking the SCTP module, though that neither unloads a running module nor disables SCTP compiled into the kernel.

Several teams found the HTTP/2 bugs independently: Wiz said its researchers, Rapid7, Ikotas Labs, Metnir and Xint all did so. Wiz said it used an AI code-scanning harness to find both HTTP/2 flaws, and Xint said its automated platform found four of its five "without human guidance". Rapid7 published a proof-of-concept for CVE-2026-123007 that needs about 128 GB of HTTP/2 traffic over one connection. Rapid7's Stephen Fewer wrote that "Alternative RCE exploitation strategies may be viable, but none are currently known." Wiz has not released its exploits but said it achieved reliable remote code execution against NGINX serving only static files.

No exploitation in the wild has been reported, and CISA's Known Exploited Vulnerabilities catalogue did not list the flaw at the time of writing. Xint said the age of some flaws means exploitation cannot be ruled out.

Administrators should upgrade and then fully restart NGINX or use its live binary upgrade, because a reload leaves the old executable running. F5 lists workarounds for only two flaws: avoiding SSI and mirror directives and variable-built proxied server names for CVE-2026-123634, and limiting mail proxy listeners to trusted networks for CVE-2026-113425. Disabling HTTP/2 blocks the two HTTP/2 flaws but would break services that depend on it, such as applications using gRPC. NGINX runs on 29.7 per cent of websites whose server software W3Techs could identify.