# Five Critical NGINX2Root Flaws Get Public Exploits as Patching Lags

- URL: https://usa-24.com/nginx-vulnerability-nginx2root-patch/
- Publisher: USA 24
- Section: Cybersecurity
- Published: 2026-11-21T17:49:52.197Z
- Updated: 2026-11-21T17:49:52.201Z
- Topics: NGINX, Web Servers, Vulnerability Management, F5, Remote Code Execution

> F5 patched five critical NGINX2Root flaws on November 18, and public proof-of-concept code followed within a day. Patching is still underway across US servers.

## Key takeaways

- F5 released out-of-band fixes for 22 vulnerabilities on November 18, 2026, including five critical NGINX flaws that can lead to unauthenticated remote code execution.
- The worst flaw, CVE-2026-123007, is an HTTP/2 flow-control bug that researchers say affects nginx versions from 1.9.5 (2015) through 1.31.8.
- Fixed open source builds are 1.30.7 for stable and 1.31.9 for mainline, while NGINX Plus fixes are 37.0.8.1 and 37.3.0.1.
- Setting "http2 off;" blocks CVE-2026-123007 and CVE-2026-123633 on nginx 1.25.1 and later, but it is only a temporary measure.
- Xint says it chained the nginx bugs with an unpatched Linux kernel SCTP flaw to reach root, and that kernel flaw has no CVE yet.

Five critical flaws in nginx, the web server software behind a large share of American websites, can let unauthenticated attackers run code on a vulnerable machine. F5 shipped fixes on Wednesday, November 18, and public proof-of-concept code appeared about a day later. Researchers call the group NGINX2Root, and this nginx vulnerability now sits in a live patching window.

## Why this nginx vulnerability spread so fast

F5 issued the fixes in an out-of-band release, which means it did not wait for its regular patch cycle. According to [SecurityWeek](https://www.securityweek.com/f5-patches-critical-nginx2root-flaws-as-poc-exploits-go-public/), the release covered 22 vulnerabilities in total, including 12 in BIG-IP. The five NGINX bugs are CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633 and CVE-2026-123634.

Xint's research team found all five and named the group nginx2root. Wiz, Ikotas Labs, Metnir and Rapid7 also reported issues to F5 independently, according to [OX Security](https://www.ox.security/blog/nginx2root-five-critical-nginx-flaws-expose-web-servers-to-remote-code-execution/).

The discovery method deserves attention from defenders. Xint's [press release](https://www.businesswire.com/news/home/20261118449389/en/PSA-Immediately-Patch-NGINX-Web-Servers-Due-to-Critical-Vulnerability-Allowing-Unauthenticated-User-RCE) says its platform found the bugs with little human guidance, using AI models that have been generally available since May. That matters because the same kind of tooling can help attackers study a patch and work out what changed, which shortens the gap between a fix and a working exploit. CISA has already flagged a [LiteLLM flaw](https://usa-24.com/litellm-cve-2026-40217-exploited/) as exploited in AI attacks, a sign that AI tooling is now part of the attack surface.

Xint's co-founder and CEO, Brian Pak, said in the same press release that nginx2root is "even more exploitable with broader impact than PHP2Shell." That is a vendor's assessment, and it should be read as one. Xint also says it gave customers 24 hours' notice that a critical update was coming, without naming the target. It adds that a demo video accidentally made public had already accelerated attacker interest in its earlier research.

## Which nginx versions and products are affected

nginx is one of the most widely used web servers and reverse proxies. A DEV Community write-up says it runs roughly a third of the web, but that is a secondary estimate rather than a measured count.

F5 rates each flaw 9.2 under CVSS 4.0 (Critical) and 8.1 under CVSS 3.1 (High), according to [Cloudflare's analysis](https://blog.cloudflare.com/nginx2root/). Exposure depends on which build and license tier a server runs, as the table below shows.

| Product or branch | Fixed version | Status |
|---|---|---|
| NGINX Open Source, stable | 1.30.7 | Patched in this release |
| NGINX Open Source, mainline | 1.31.9 | Patched in this release |
| NGINX Plus | 37.0.8.1 or 37.3.0.1 | Patched in this release |
| NGINX Plus R34 through R36 | No fixed build | Move to a fixed 37.x release |
| Older open source builds, back to 1.9.5 (2015) | Upgrade to a fixed build | CVE-2026-123007 affects versions through 1.31.8, per researchers |

Any US company, agency, hosting provider or developer running self-managed nginx, nginx Plus or distribution nginx packages is potentially exposed. Researchers point to deployments that expose HTTP/2, HTTP/3, mail proxy or DNS resolver features as the most at risk. Xint also says AWS, Azure and Google Cloud collaborated on the patch.

## How the NGINX2Root bugs could lead to root

The worst bug, CVE-2026-123007, is an HTTP/2 flow-control flaw that can corrupt memory inside an NGINX worker process, according to [BleepingComputer](https://www.bleepingcomputer.com/news/security/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers/) and OX Security. Xint says the most severe of the five allows unauthenticated remote code execution on the most common nginx configuration. Public proof-of-concept exploits have been published, and one exists specifically for CVE-2026-123007, according to [Tenable](https://www.tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx).

The ASLR condition is the main point of dispute. F5 says code execution requires address space layout randomization (ASLR) to be disabled or bypassed. Some reports say ASLR bypasses have already been demonstrated, which would remove that barrier, as [Offseq Radar](https://radar.offseq.com/threat/f5-patches-critical-nginx2root-flaws-as-poc-exploits-go-public-417dbc2f85edd439) notes. ASLR is a standard memory protection on modern Linux systems, but until more detailed write-ups appear, administrators should not assume it alone protects them.

The root-level threat is a second step. Xint says it chained the nginx bugs with a separate Linux kernel SCTP local privilege escalation flaw to gain root. That kernel flaw has no CVE and no patch yet, and Xint is withholding most technical details. Local privilege escalation requires code execution on the machine first, so the chain is most dangerous when nginx hands an attacker that initial foothold.

F5's November 18 release also fixed five additional NGINX flaws, including one that causes an infinite loop when reading a request body over TLS 1.3.

## How to patch nginx 1.31.9 and NGINX Plus today

Patch first and sort out the details second. Brotli2Shell, a separate web-facing flaw, is already being exploited and carried a [federal deadline of November 10](https://usa-24.com/cve-2026-111497-brotli-flaw-exploited/), so web-server bugs are moving fast this month.

- Inventory every nginx instance, including those bundled in appliances, containers and Linux distribution packages. Cloudflare recommends starting there.
- Upgrade open source installs to 1.30.7 (stable) or 1.31.9 (mainline). Upgrade NGINX Plus to 37.0.8.1 or 37.3.0.1.
- If your distribution ships nginx, install its fixed package. AlmaLinux has backported the patches to its NGINX packages, according to BleepingComputer. Red Hat Enterprise Linux is presumably getting backports too, but the research for this story did not confirm it, so check Red Hat's advisories directly.
- Restart nginx or complete a binary upgrade so the patched code is actually running.
- Move NGINX Plus R34 through R36 deployments to a fixed 37.x release, because those branches have no fixed build.
- If you cannot patch right away, add "http2 off;" to your configuration. Cloudflare says that blocks CVE-2026-123007 and CVE-2026-123633 on nginx 1.25.1 and later. Treat that as a stopgap, not a fix.
- Review whether mail proxy or DNS resolver features are in use, since those features carry their own exposure, as Tenable advises.

## Is my nginx server vulnerable and what should consumers do

The fastest check is the version. Run nginx -v on each server and compare the output with the fixed builds. Any open source install older than 1.30.7 on the stable branch or older than 1.31.9 on mainline should be treated as unpatched.

Distribution packages can carry a fixed fix under an older-looking version number, so check your vendor's advisory rather than relying on the upstream version alone. Servers that sit on the public internet should go first, followed by any internal proxies that handle mail or DNS traffic.

For consumers, the exposure is indirect. People are affected only through the websites and online services that run nginx, and there is no action to take beyond installing normal software updates on their own devices.

## What to watch next

The research behind this story found no confirmed in-the-wild exploitation of these flaws. F5 also says none of the disclosed flaws had been exploited in active attacks at release, according to SecurityWeek. The research also turned up no CISA Known Exploited Vulnerabilities listing for these CVEs.

That can change quickly. A KEV entry would set federal patch deadlines and push more administrators to act. The kernel SCTP flaw is the piece that would turn an nginx foothold into root, so a kernel fix would reduce the chain's risk considerably. Xint has not said whether it will publish full technical details after a kernel fix, and that answer will shape how fast defenders can test their own systems.

The next few days will show whether this stays a patching problem or becomes an exploitation campaign. Operators who patch this week will be in a better position either way, and anyone still running NGINX Plus R34 through R36 or pre-fix builds should treat the window as already open.

## Frequently asked questions

### Which nginx version fixes the NGINX2Root vulnerabilities?

F5's fixed open source versions are 1.30.7 for the stable branch and 1.31.9 for mainline. The fixed NGINX Plus builds are 37.0.8.1 and 37.3.0.1. NGINX Plus R34 through R36 have no fixed build and need to move to a fixed 37.x release.

### Is the nginx2root vulnerability being exploited in the wild?

The research for this story found no confirmed in-the-wild exploitation, and F5 said none of the disclosed flaws had been exploited in active attacks at release. No CISA Known Exploited Vulnerabilities listing turned up for these CVEs. Public proof-of-concept exploits do exist, so the risk is rising even without confirmed attacks.

### How can I protect nginx if I cannot patch right away?

Add "http2 off;" to your nginx configuration. Cloudflare says that setting blocks CVE-2026-123007 and CVE-2026-123633 on nginx 1.25.1 and later. It is a temporary measure, so you should still install the fixed version as soon as you can.

### Does the nginx vulnerability affect ordinary consumers?

Consumers are affected only indirectly, through websites and online services that run nginx. There is no specific action to take beyond normal software updates on the devices you control.

## Sources

1. [F5 Patches Critical NGINX2Root Flaws as PoC Exploits Go Public — SecurityWeek](https://www.securityweek.com/f5-patches-critical-nginx2root-flaws-as-poc-exploits-go-public/)
2. [Critical NGINX 'NGINX2Root' bugs let attackers hijack servers — BleepingComputer](https://www.bleepingcomputer.com/news/security/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers/)
3. [nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them — Cloudflare Blog](https://blog.cloudflare.com/nginx2root/)
4. [NGINX2Root: 5 Critical NGINX RCE Vulnerabilities & CVE Fixes — OX Security](https://www.ox.security/blog/nginx2root-five-critical-nginx-flaws-expose-web-servers-to-remote-code-execution/)
5. [NGINX2Root FAQ: Five vulnerabilities in NGINX (CVE-2026-123007) — Tenable](https://www.tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx)
6. [PSA: Immediately Patch NGINX Web Servers Due to Critical Vulnerability Allowing Unauthenticated User RCE — Xint, via Business Wire](https://www.businesswire.com/news/home/20261118449389/en/PSA-Immediately-Patch-NGINX-Web-Servers-Due-to-Critical-Vulnerability-Allowing-Unauthenticated-User-RCE)
7. [nginx2root: AI Found Five Critical nginx Flaws — Patch to 1.30.7 or 1.31.9 Before Attackers Do — DEV Community](https://dev.to/shakeelahmed/nginx2root-ai-found-five-critical-nginx-flaws-patch-to-1307-or-1319-before-attackers-do-5bkf)
8. [F5 Patches Critical NGINX2Root Flaws as PoC Exploits Go Public — Offseq Radar](https://radar.offseq.com/threat/f5-patches-critical-nginx2root-flaws-as-poc-exploits-go-public-417dbc2f85edd439)
