Skip to content

Vulnerabilities & Patches

F5 patches critical NGINX nginx2root flaws that chain with Linux bug for root access

Researchers demonstrated unauthenticated remote code execution and root access through a Docker container escape.

https://breach-signal.com/vulnerabilities/f5-patches-nginx-nginx2root-root-access/

Share

Key facts

  • Researchers demonstrated that the NGINX flaws combine with a Linux kernel bug to give an attacker root access.
  • F5 fixed the flaws in NGINX Open Source 1.30.7 stable and 1.31.9 mainline.
  • CVE-2026-123007 affects all NGINX versions from 1.31.8 down to 1.9.5, released in 2015.
  • The separate Linux kernel vulnerability affects the SCTP subsystem and can escape an NGINX Docker container to gain root privileges on the host.

F5 patched two severe NGINX flaws known as nginx2root that allow attackers without credentials to run code on exposed web servers, and Xint said updates arrived through F5, AWS, Azure and GCP on November 18, 2026.

CVE-2026-123007 reaches every NGINX version from 1.31.8 back to 1.9.5, which came out in 2015, while CVE-2026-123633 spans versions 1.19.7 through 1.31.8. Infosecurity Magazine places one HTTP/2 flaw in 2015 and the other in 2020, which conflicts with other sources pointing to 1.9.5 and 1.19.7 as the earliest affected versions. F5 issued fixes for NGINX Open Source 1.30.7 stable and 1.31.9 mainline. Users of NGINX Plus should move to versions 37.0.8.1 or 37.3.0.1.

BankInfoSecurity names different patched NGINX Plus releases, 37.3.0 and 37.0.8, which conflicts with other reports.

CVE-2026-123007 is a flow-control defect that can corrupt memory within an NGINX worker process. CVE-2026-123633 is a use-after-free condition that hits NGINX when it takes HTTP/2 traffic and forwards requests to a backend server. Wiz showed unauthenticated remote code execution on NGINX delivering standard static files through HTTP/2 with TLS.

The two HTTP/2 flaws were found independently by Xint, Wiz, Ikotas Labs, Metnir and Rapid7, while Xint separately uncovered three additional NGINX remote code execution issues. Rapid7 reported CVE-2026-123007 to F5 on November 11, and Xint found it separately plus four more flaws through an automated scan without human guidance.

Three additional use-after-free bugs target mail proxy authentication, HTTP/3 reverse proxying and DNS resolution that uses subrequests. CVE-2026-123634 requires resolver, request-derived proxy_pass, mirror and mirror_request_body set to off to coexist in the configuration. CVE-2026-121810 comes from closing a QUIC connection during an active HTTP/3 request, and CVE-2026-113425 activates during mail proxy auth_http login when no valid credentials are provided.

Researchers showed that the NGINX defects link with a Linux kernel flaw to grant an attacker root access. Xint proved root access is possible by linking CVE-2026-123007 to a distinct Linux kernel weakness that hits the SCTP subsystem and can break out of an NGINX Docker container to obtain root rights on the host machine.

That kernel weakness goes back to Linux 4.15 from 2018 and had no CVE or patch when disclosed. Investigators leveraged it to obtain root access on cloud hosts and from within a Docker container, and Xint uncovered a sixth flaw, a Linux kernel SCTP use-after-free that may turn into a double free, as a path to root.

Rapid7 released a proof-of-concept exploit for CVE-2026-123007, whereas Xint and Wiz created exploits for the five flaws but did not publish them. Censys recreated CVE-2026-123007 in a lab setting using unencrypted HTTP/2 and without the heavy traffic volume Rapid7 described.

There is no evidence of any flaw being exploited in the wild, and none appeared on CISA’s Known Exploited Vulnerabilities catalog as of November 19. Xint stated that every one of the five flaws has a working exploit, although the requirements and affected versions vary, and added that it saw no evidence of wild exploitation when it published, though the flaws’ age means active use cannot be excluded.

Censys put the number of potentially exposed NGINX services for CVE-2026-123007 at roughly 8.8 million as of November 19. The firm also said more than 511,000 previously exposed services have been patched or mitigated, while 104 million services do not reveal their versions.

Censys also flagged roughly 9 million NGINX services running affected versions with HTTP/2 enabled, plus 103 million more that hide their versions. Xint said 98.9% of NGINX hosts with identifiable versions were running affected software as of November 10, 2026.

Infosecurity Magazine says NGINX runs on more than 225 million websites globally. BankInfoSecurity points to W3Techs data showing nearly 30%, and Itnews cites 29.7%.

Florian Roth said claims based only on version numbers are misleading since they overlook whether HTTP/2 is active or fixes have been backported. Roth added that exploitation calls for non-default configurations and most NGINX deployments are not in immediate danger, stating, “it’s worse than Node2Shell and Java2Shell, but doesn’t appear to be an imminent threat for most NGINX deployments.” Johannes Ullrich, dean of research at SANS Technology Institute, said large companies probably cannot patch every NGINX instance before exploits surface and recommended automating patch deployment, reducing internet-facing systems and restricting data and resources each application can reach.

F5 says remote code execution is possible only when ASLR is turned off or defeated, while Wiz says CVE-2026-123007 and CVE-2026-123633 can defeat ASLR. With ASLR off or bypassed, any of the five flaws can permit remote code execution using NGINX worker process privileges.

Rapid7’s exploit requires roughly 128 gigabytes of HTTP/2 traffic, an x86-64 glibc routine and ASLR defeat through leaked heap addresses. It takes two minutes to one hour and breaks down on slow links because NGINX limits connections to one hour. BankInfoSecurity reported that Rapid7 said exploitation takes two and a half minutes without authentication on HTTP/2 and TLS, although it is more difficult in practice.

Administrators should upgrade right away or temporarily turn off HTTP/2, though this mitigation addresses only the two nginx2root flaws. Administrators should upgrade and restart NGINX since reloading the configuration does not swap out the running executable. People using distribution packages should look for backported fixes. Xint customers got 24-hour notice of a critical update without being told the target, and F5 requested limits on pre-distribution to keep malicious actors from learning about it.

F5’s update also covers CVE-2026-118899, which lets an unauthenticated attacker cause a worker to loop while reading a TLS 1.3 request body, resulting in denial of service. One update addresses five flaws that lead to SSL/TLS termination problems, certificate verification bypasses, segmentation faults, terminated worker processes and denial of service. NGINX is part of F5 products including NGINX Instance Manager, NGINX Ingress Controller and NGINX Gateway Fabric, and updates for some are out while others remain pending.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *