# NGINX2Root: F5 publishes fixed versions for five critical NGINX flaws

NGINX Open Source 1.30.7 and 1.31.9 and NGINX Plus 37.0.8.1 and 37.3.0.1 fix five remote code execution flaws. NGINX Plus R33 to R36 get no patch at all.

Source: https://junglewise.ai/news/f5-patches-five-nginx-flaws-after-researchers-publish-working-exploits  
Byline: Junglewise News Desk, https://junglewise.ai/news  
Topic: Vulnerabilities and exploitation  
Published: 19 November 2026. Updated: 19 November 2026  
Reading time: 6 min

![Close-up of server rack drive bays with status lights](https://images.unsplash.com/photo-1762163516269-3c143e04175c?ixid=M3w0NDU4NjF8MHwxfHNlYXJjaHwxfHxzZXJ2ZXIlMjByYWNrJTIwY2xvc2UtdXB8ZW58MXwwfHx8MTc5NTA1MTMzM3ww&ixlib=rb-4.1.0&w=1600&q=80&fm=jpg&fit=crop)

Picture: Photo by [Domaintechnik](https://unsplash.com/@fslfsl?utm_source=junglewise&utm_medium=referral) on [Unsplash](https://unsplash.com/?utm_source=junglewise&utm_medium=referral)

F5 has published the fixed releases for the five critical [NGINX](/threats/vendors/nginx) vulnerabilities disclosed on 18 November 2026. NGINX Open Source users should move to 1.30.7 on the stable branch or 1.31.9 on mainline, [according to nginx.org's security advisories](https://nginx.org/en/security_advisories.html). NGINX Plus is fixed in 37.0.8.1 and 37.3.0.1, and releases R33 through R36 have no patch at all: those deployments have to move to a 37.x release, [Tenable reported](https://tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx).

All five flaws can lead to unauthenticated remote code execution, meaning an attacker who can reach the server over the network can run commands on it without a password, [according to CERT-EU](https://cert.europa.eu/publications/security-advisories/2026-022). The code runs with the privileges of the NGINX worker process, not root. One research team, Xint, chained the worst of the five with a separate and still unpatched Linux kernel bug to reach root on the host, which is where the name NGINX2Root comes from. Neither F5 nor nginx.org uses that name.

The same out-of-band update also fixed five further NGINX vulnerabilities of lower severity, bringing the total to ten CVEs, Tenable reported. The five critical CVEs do not appear on the United States Cybersecurity and Infrastructure Security Agency (CISA) Known Exploited Vulnerabilities catalog, and there were no reports of exploitation in the wild as of 18 November 2026, although working exploits for the critical five exist and one is public.

Scale is the complicating factor. NGINX handles traffic for roughly a third of all websites, [CyberScoop reported](https://cyberscoop.com/nginx-critical-vulnerabilities-exploits), and a Shodan snapshot by Xint found 98.9% of 11.94 million NGINX hosts whose version could be identified were running affected releases. That figure counts version strings rather than confirmed vulnerable configurations, and it cannot see HTTP/2 usage or distribution backports, so it overstates real exposure.

## What to do now

1. **Upgrade.** For NGINX Open Source, move to 1.30.7 (stable) or 1.31.9 (mainline). For NGINX Plus, move to 37.0.8.1 or 37.3.0.1. If you are on R33 through R36, there is no fix for your branch and you need to move to a 37.x release. Prioritise anything reachable from the internet, as CERT-EU recommends.
2. **Restart NGINX after upgrading.** A configuration reload does not swap out the running executable, so the old vulnerable binary keeps serving traffic until you actually restart the service.
3. **Find the instances you forgot about.** NGINX usually arrives inside something else: container images, appliances, load balancers and application stacks nobody installed by hand. Each CVE has its own earliest affected release, reaching as far back as 0.5.x in the case of the mail proxy bug and 1.9.5 for the HTTP/2 one, so old installations are not automatically out of scope.
4. **Do not treat disabling HTTP/2 as a blanket workaround.** It covers only CVE-2026-123007 and CVE-2026-123633. Xint has warned that it does nothing for CVE-2026-123634, CVE-2026-121810 or CVE-2026-113425.
5. **If you genuinely cannot patch yet, mitigate per feature.** Remove `http2` from `listen` directives or set `http2 off;` for the two HTTP/2 bugs; remove QUIC and HTTP/3 listeners for CVE-2026-121810; bind mail listeners to loopback or restrict them with a firewall for CVE-2026-113425; point `proxy_pass` at a fixed upstream group and disable `mirror` where it is not needed for CVE-2026-123634. Disabling `mirror` alone does not make a server safe from that last one. These are stopgaps, not fixes.
6. **Block the SCTP kernel module on hosts that do not use it.** Xint recommends this until a fix lands for the kernel privilege escalation flaw it used to escape a worker process and, in its demonstration, a Docker container.
7. **Watch the error log for worker crashes.** A `worker process ... exited on signal` message can indicate exploitation attempts. CERT-EU is clear this is not a high-fidelity indicator of successful code execution, so follow up in process creation logs.

Other F5 products are worth a look too. F5 said BIG-IP and F5OS were found not vulnerable, while its cloud services were still being evaluated.

## Technical details

The headline flaw is **CVE-2026-123007**, an arithmetic bug in NGINX's HTTP/2 flow control. HTTP/2 uses a credit system to track how much data a client will accept. When a client cancels a request while response data is still queued, NGINX returns the unused credit without checking the running total against the protocol maximum. The counter wraps, the result is later treated as a negative response length, and the outcome is an out-of-bounds write on the heap.

Severity ratings differ. F5 rates all five critical flaws CVSSv4 9.2 and describes CVE-2026-123007 as an integer underflow; CERT-EU records it as an integer overflow with a CVSS score of 8.1. nginx.org classifies it as major severity. The only precondition is HTTP/2 enabled on a listening port, and the bug has been present since HTTP/2 support arrived in nginx 1.9.5 in 2015. Wiz confirmed code execution against an instance serving nothing but static content.

The other four critical flaws are use-after-free bugs, each CVSS 8.1 at CERT-EU:

- **CVE-2026-123633**: connection draining closes an active HTTP/2 connection while NGINX is opening an upstream connection. Needs HTTP/2 and upstream forwarding. Also fixed in NGINX Plus 37.0.7.1 and 37.2.0.1.
- **CVE-2026-121810**: the HTTP/3 equivalent, where a QUIC connection is drained during stream creation and upstream connection.
- **CVE-2026-123634**: in processing of the DNS resolver waiting list. Needs a resolver configured, a `proxy_pass` destination built from request data, and `mirror` with `mirror_request_body off`.
- **CVE-2026-113425**: triggered when a client closes the connection during an `auth_http` lookup. Needs a mail proxy with `proxy on` and `auth_http`.

The five lower-severity CVEs in the same update are CVE-2026-118899 (TLSv1.3, 8.7), CVE-2026-120993 (stream_ssl, 6.9), CVE-2026-125283 (map/regex, 6.9), CVE-2026-123640 (ssl_preread, 6.9) and CVE-2026-120967 (stream_ssl, 6.3).

Affected versions run from NGINX Open Source mainline 1.9.5 through 1.31.8 and the 1.30.x stable branch including 1.30.6, plus NGINX Plus 37.0.0 to 37.0.7.1, 37.1.0 to 37.2.0.1, and R34, R35 and R36.

Rapid7 researcher Stephen Fewer published a technical analysis on 18 November 2026 and released a public proof of concept on GitHub (`sfewer-r7/CVE-2026-123007`), including a crash trigger and a full unauthenticated RCE exploit demonstrated against NGINX 1.31.8 in Docker with HTTP/2 over TLS. The attack is constrained: it needs roughly 128 gigabytes of HTTP/2 traffic, mostly control frames carrying no payload, and it must defeat address space layout randomisation by recovering heap addresses from server responses. In testing it completed in two and a half minutes across a fast local network, in around two minutes on a 10-gigabit link, and in 17 minutes where only 1 gigabit was available. NGINX drops connections after an hour unless configured otherwise, so a link below roughly 300 megabits per second cannot deliver the traffic in time, and HTTP/2-terminating proxies in front of the server make success unlikely. The exploit also depends on an optimised memory-copy routine in the GNU C Library used on x86-64 chips with certain AVX-512 features. Rapid7 said other routes may exist but none are currently known.

Xint published demo videos while omitting the final steps needed to reproduce the full exploits, and is withholding most technical details of the kernel SCTP use-after-free until a patch exists. No CVE had been assigned to that kernel flaw as of 18 November 2026. Wiz confirmed working exploits exist but chose not to publish them.

F5's advisory credits Fewer alongside Wiz Research, Xint and Ikotas Labs. Wiz worked with Ikotas Labs, Metnir and Rapid7 and independently found two of the same flaws. Xint says it found the bugs on 11 October 2026 and reported them to F5 through HackerOne on 16 October 2026, using an automated testing harness run without human guidance: pointed at about 50,000 lines of NGINX code, it produced high-severity findings within 90 minutes and a working exploit roughly 10 minutes later.

"We're grateful for the collaboration with project maintainers to get a patch released quickly," said Brian Pak, co-founder and CEO of Xint.

## What changed

- 19 November 2026: Added the official fixed versions, noted that NGINX Plus R33 to R36 get no patch, listed five more CVEs in the same update, and corrected the HTTP/2 workaround advice.

## On Junglewise Threat Intelligence

- [NGINX](https://junglewise.ai/threats/vendors/nginx)

## The story so far

- [Public exploits land for NGINX2Root flaws as F5 reports no attacks yet](https://junglewise.ai/news/public-exploits-land-for-nginx2root-flaws-as-f5-reports-no-attacks-yet)

## Related articles

- [Node2Shell: Siemens names SCADA and building management products affected by Brotli flaw](https://junglewise.ai/news/node2shell-siemens-names-scada-and-building-management-products-affected-by)
- [Java4Shell: attackers begin probing OpenJDK flaw as vendor advisories pile up](https://junglewise.ai/news/java4shell-attackers-begin-probing-openjdk-flaw-as-vendor-advisories-pile-up)
- [Broadcom patches critical vCenter bypass that Mandiant says a China-linked group exploited](https://junglewise.ai/news/broadcom-patches-critical-vcenter-bypass-that-mandiant-says-a-china-linked-group)
- [PHP2Shell: Palo Alto firewall management interfaces attacked for remote code execution](https://junglewise.ai/news/php2shell-palo-alto-firewall-management-interfaces-attacked-for-remote-code)
