All News Updates
Company NewsCybersecurity

NGINX2Root: Five Critical NGINX Vulnerabilities Let Attackers Take Over Servers — Patch Now

6 min read
NGINX2Root: Five Critical NGINX Vulnerabilities — Patch Now

NGINX2Root: Five Critical NGINX Vulnerabilities Let Attackers Take Over Servers — Patch Now

Security researchers have disclosed five critical vulnerabilities in NGINX, collectively dubbed “NGINX2Root,” that could allow unauthenticated remote attackers to execute code on vulnerable web servers. F5, which owns NGINX, has released patches, and administrators are urged to update immediately.

The most severe of the five, CVE-2026-123007, affects NGINX’s HTTP/2 implementation and has existed since HTTP/2 support was introduced in version 1.9.5 in 2015.

What happened

On 18 November 2026, F5 released an out-of-band security update fixing ten vulnerabilities in NGINX Open Source and NGINX Plus. Five of these have been grouped under the name NGINX2Root by researchers at Xint (Theori).

F5 rates each of the five NGINX2Root vulnerabilities as CVSS v3.1 8.1 (High) and CVSS v4.0 9.2 (Critical).censys

The five vulnerabilities are all independent memory-corruption bugs affecting different NGINX features: HTTP/2, HTTP/3 (QUIC), the DNS resolver, and the mail proxy module.

The five CVEs

CVE

Affected feature

Trigger

Memory flaw

Severity (F5)

CVE-2026-123007

HTTP/2 (ngx_http_v2_module)

Undisclosed traffic pushes the flow-control window past its limit

Heap buffer overflow

9.2 Critical

CVE-2026-123633

HTTP/2 proxying to backend

Crafted request with worker low on worker_connections

Use-after-free

9.2 Critical

CVE-2026-123634

Resolver + proxied server name with variables + SSI/mirror subrequest

Crafted HTTP request

Use-after-free

9.2 Critical

CVE-2026-121810

HTTP/3 (QUIC) proxying to backend

Remote, unauthenticated traffic; worker low on worker_connections

Use-after-free

9.2 Critical

CVE-2026-113425

Mail proxy (ngx_mail_proxy_module)

Undisclosed traffic during login; no valid credentials needed

Use-after-free

9.2 Critical

The most urgent: CVE-2026-123007

CVE-2026-123007 is the most urgent of the five because it only requires HTTP/2 to be enabled — a configuration common on HTTPS-serving sites.

The flaw has existed since NGINX introduced HTTP/2 support in version 1.9.5, released in 2015, meaning a very large number of servers worldwide could be affected.

Wiz Research confirmed code execution against an NGINX instance serving only static content, with no application logic or additional modules involved.

Rapid7 published a technical analysis and a public proof-of-concept (PoC) on GitHub for CVE-2026-123007.

Root access: a separate chain

On their own, each of the five NGINX vulnerabilities can lead to code execution in the NGINX worker process, but not automatically root access.

Researchers at Xint demonstrated that CVE-2026-123007 can be chained with a separate, unpatched Linux kernel SCTP use-after-free vulnerability (no CVE assigned as of 18 November) to escalate from NGINX worker privileges to root on the host.

The chain also worked from inside a Docker container, meaning containerised NGINX deployments could be at risk of host compromise.

Important: Patching NGINX closes the way in, but the Linux kernel vulnerability requires its own kernel update.

Affected NGINX versions

NGINX product

Affected versions

Fixed version

NGINX Open Source (stable)

Before 1.30.7

1.30.7 and later.

NGINX Open Source (mainline)

1.31.0–1.31.8

1.31.9 and later.

NGINX Open Source (older)

1.9.5–1.29.x (for CVE-2026-123007)

Move to 1.30.7+ or vendor-patched package.

NGINX Plus 37.x

Before fixed releases

37.0.8.1 or 37.3.0.1.

NGINX Plus R33–R36

All versions

No patch available; move to 37.x.

Note: Version numbers alone do not determine patch status. For example, 1.31.8 is affected while 1.30.7 is not, even though 1.31.8 is the higher number.

Exploit status

  • CVE-2026-123007: Public PoC available on GitHub (Rapid7).

  • CVE-2026-123633, CVE-2026-123634, CVE-2026-113425: Use-after-free and worker crash confirmed in research.

  • CVE-2026-121810: Not independently reproduced yet.

  • Exploitation in the wild: No evidence of exploitation as of 18 November 2026.

  • Zero-day status: No; the bugs were found on 11 October 2026 and reported to F5 via HackerOne on 16 October, then published after coordinated release.

How to check if you’re affected

Check NGINX version

bash

nginx -v

If the version shown is 1.30.7 or later (stable), or 1.31.9 or later (mainline), the server is already patched.

Check HTTP/2 is enabled

bash

grep -r "http2" /etc/nginx/

If HTTP/2 is enabled, the server is potentially exposed to CVE-2026-123007 and CVE-2026-123633.

Check HTTP/3 (QUIC) is enabled

bash

grep -r "quic" /etc/nginx/

If HTTP/3 is enabled, the server is potentially exposed to CVE-2026-121810.

Check mail proxy is enabled

bash

grep -r "mail" /etc/nginx/

If the mail proxy is enabled with proxy on and auth_http, the server is potentially exposed to CVE-2026-113425.

How to patch

Ubuntu/Debian (nginx.org repository)

bash

sudo apt-get update
sudo apt-get install --only-upgrade -o Dpkg::Options::=--force-confold nginx

Then restart NGINX:

bash

sudo systemctl restart nginx

Verify:

bash

nginx -v
sudo nginx -t

RHEL/CentOS/AlmaLinux

bash

sudo yum update nginx

or

bash

sudo dnf update nginx

Then restart:

bash

sudo systemctl restart nginx

Docker

Rebuild the image with the fixed NGINX version and redeploy:

bash

docker build -t my-nginx .
docker run -d -p 80:80 my-nginx

Kubernetes

Update the NGINX image in your deployment manifest and roll out:

bash

kubectl set image deployment/nginx nginx=nginx:1.31.9
kubectl rollout status deployment/nginx

Temporary mitigations

If immediate patching is not possible, the following mitigations can reduce risk — but each covers only some of the vulnerabilities.

Feature / Component

Mitigation

Covers

HTTP/2

Disable HTTP/2

CVE-2026-123007, CVE-2026-123633 only.

HTTP/3 (QUIC)

Remove the QUIC/HTTP/3 listeners

CVE-2026-121810.

Mail proxy

Bind mail listeners to loopback or restrict access with a firewall

CVE-2026-113425.

Resolver with request-derived proxy_pass

Point proxy_pass at a fixed upstream group and turn off mirror where not needed

CVE-2026-123634.

Important: Disabling HTTP/2 does not protect against CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425, so it is not advised as a blanket workaround.

For the unpatched Linux kernel LPE, until a kernel fix is available, Xint recommends blocking the SCTP module on hosts that do not use it.

Remediation checklist

  1. Inventory NGINX deployments. Include bare-metal, VM, container, and Kubernetes environments.

  2. Identify affected versions. Prioritise internet-facing servers.

  3. Check enabled features. HTTP/2, HTTP/3, resolver, mail proxy.

  4. Apply vendor patches. Use the fixed release from F5, nginx.org, or your distribution vendor.

  5. Restart NGINX. A configuration reload does not replace the running executable.

  6. Rebuild container images. Redeploy updated images rather than relying on an old base layer.

  7. Verify the running version. Confirm the fixed build is actually in use.

  8. Monitor for suspicious activity. Watch for repeated worker exits and unexpected processes.

  9. Apply kernel updates when available. The Linux kernel LPE requires its own patch.

Frequently asked questions

What is NGINX2Root?

NGINX2Root is the name given by researchers at Xint (Theori) to five critical memory-corruption vulnerabilities in NGINX that can allow unauthenticated remote code execution.

Which CVEs are involved?

CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425.

Is my NGINX server affected?

If you run NGINX with HTTP/2, HTTP/3, a resolver with variable server names, or a mail proxy, and your version is below the fixed release, you may be affected.

Does disabling HTTP/2 fix NGINX2Root?

No. Disabling HTTP/2 only mitigates CVE-2026-123007 and CVE-2026-123633. It does not address the other three vulnerabilities.

Can attackers gain root access?

Only by chaining one of the NGINX vulnerabilities with a separate, unpatched Linux kernel SCTP use-after-free vulnerability. Patching NGINX alone does not fix the kernel issue.

What should I do first?

Check your NGINX version, identify enabled features, apply the vendor patch, restart NGINX, and verify the running version.

Sources

#nginx2root#nginx-vulnerability#cve-2026-123007#cve-2026-123633#cve-2026-123634#cve-2026-121810#cve-2026-113425#remote-code-execution#cybersecurity-news#f5
Share This Story
Pass helpful engineering insights to your peers

Feedback & Discussion

Have questions or insights? Share your thoughts below.

0 Comments
Leave a Comment
Respectful discourse only. Managed by Global IT Services team.
Loading comments…