- November 18, 2026
NGINX2Root: Critical Vulnerability in Nginx
NGINX2Root, a set of vulnerabilities discovered by multiple researchers was reported in Nginx, a widely used web server software package. These CVEs allow an unauthenticated threat actor to achieve remote code execution, and affected organizations should update their systems as soon as possible.
Executive Summary
On November 18th, 2026, F5 released patched versions of NGINX to address five critical vulnerabilities, each of which independently allows an unauthenticated, remote attacker to execute arbitrary code with the privileges of the NGINX worker process. Researchers at Wiz and Xint Security disclosed the flaws concurrently with the patch release.
The most severe vulnerabilities, CVE-2026-123633 and CVE-2026-123007, are separate memory corruption bugs in HTTP/2 traffic processing that lead to out-of-bounds writes. One is a heap overflow, and the other is a use-after-free, but both can lead to remote code execution. Both affect recent NGINX releases and require only that HTTP/2 is enabled on the listener. Both research teams that discovered these CVEs confirmed working exploits but have not publicly released them.
Beazley Security recommends that affected organizations apply the patched NGINX releases as soon as possible. Where upgrading is not immediately feasible, disable HTTP/2 on all affected listeners as an interim measure. Organizations running NGINX in front of internet-facing services should treat this as a priority.
Affected Systems or Products
Product | Affected Versions | Fixed Versions |
|---|---|---|
NGINX OSS (stable) | 1.9.5 through 1.30.6 | 1.30.7 |
NGINX OSS (mainline) | 1.9.5 through 1.31.8 | 1.31.9 |
NGINX Plus (CVE-2026-123633) | All releases prior to fix | R37 P0.7.1, R37 P2.0.1 |
NGINX Plus (CVE-2026-123007) | All releases prior to fix | R37 P0.8.1, R37 P3.0.1 |
Mitigations / Workarounds
Upgrading to a fixed release is the only complete remediation. Where upgrading is not immediately feasible, the following configuration changes reduce exposure. These mitigation steps were provided by the organizations that discovered the flaws and F5 has not provided any official workarounds at the time of writing. Each workaround addresses only the specific CVE noted; organizations exposed to multiple flaws must apply multiple mitigations.
CVE-2026-123007 and CVE-2026-123633 (HTTP/2): Set
http2 off;or remove thehttp2parameter fromlistendirectives. Note that gRPC clients require HTTP/2 and will break.CVE-2026-121810 (HTTP/3): Remove QUIC listeners, disable HTTP/3, and clear any
Alt-Svcheaders advertising HTTP/3 support.CVE-2026-123634 (resolver + mirror): Replace request-time DNS resolution with fixed upstream groups. The Xint advisory notes that setting
mirror_request_body ondoes not mitigate this flaw.CVE-2026-113425 (mail proxy): Bind mail listeners to loopback or restrict access by firewall.
Kernel SCTP chain (local escalation to root): Block the SCTP module with
install sctp /bin/falsein/etc/modprobe.d/. This does not automatically unload a module already loaded or disable a kernel with SCTP built in.
After applying any of these changes, restart NGINX rather than reloading it. A reload does not replace the running binary, and existing connections may persist on old worker processes.
Patches
Product | Fixed Version |
|---|---|
NGINX OSS (stable) | 1.30.7 |
NGINX OSS (mainline) | 1.31.9 |
NGINX Plus (CVE-2026-123633) | R37 P0.7.1, R37 P2.0.1 |
NGINX Plus (CVE-2026-123007) | R37 P0.8.1, R37 P3.0.1 |
Linux distributions may backport the fixes without changing the version string reported by nginx -v. Compare the full package version against the distribution's own security advisory rather than relying on the NGINX version alone.
Technical Details
CVE-2026-123007 sits in the HTTP/2 flow-control path. When NGINX refunds bytes to the send window, the refund can exceed the HTTP/2 maximum window size. An unsigned bounds check wraps, producing a negative length that is passed to the TLS send path, resulting in an out-of-bounds memory copy. Wiz reports that ASLR does not prevent exploitation.
CVE-2026-123633 is a use-after-free in HTTP/2 connection handling. When NGINX operates as a reverse proxy, an HTTP/2 connection can remain on the reusable-connection list after a request begins. If the connection is closed mid-request, the memory backing it is freed while the request still holds a reference. Wiz describes this as most relevant when free connection slots run low.
CVE-2026-123634 involves the interaction of the resolver, a variable-based proxy_pass, and the mirror directive with mirror_request_body off. It does not require HTTP/2.
CVE-2026-121810 is the HTTP/3 (QUIC) counterpart to CVE-2026-123633, affecting upstream-proxying configurations on NGINX builds with HTTP/3 support.
CVE-2026-113425 affects the NGINX mail proxy module when configured with proxy on and auth_http. It has been present since NGINX 0.5.15.
Kernel SCTP chain: Xint Security demonstrated that an attacker who achieves code execution as the NGINX worker can exploit a use-after-free in the Linux kernel's SCTP implementation (present since Linux 4.15, released in 2018) to escalate to root. The researchers report that the escalation also works from within a Docker container. This kernel vulnerability does not yet have a CVE identifier.
How Beazley Security is responding
Beazley Security is monitoring client perimeter devices through our Exposure Management Platform to identify impacted devices and support organizations in remediation of any issues found.
We are also conducting threat hunts across our MDR environment to detect potential exploitation attempts against our clients.
If you believe your organization may have been impacted by this attack campaign and need support, please contact our Incident Response team.