November 18, 2026

nginx2root: Critical nginx vulnerabilities, including one RCE [CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425]

TL;DR

  • nginx2root is a set of five critical nginx vulnerabilities, disclosed on November 18, 2026. Each lets an unauthenticated attacker run commands on the server.
  • The worst, CVE-2026-123007, affects any nginx with HTTP/2 enabled and reachable, in every release from 1.9.5 (2015) through 1.31.8.
  • A Linux kernel SCTP flaw can be chained with any one of the vulnerabilities to get root on the host, including from inside a Docker container.
  • Update to nginx 1.31.9 (mainline) or 1.30.7 (stable). Disabling HTTP/2 blocks only CVE-2026-123007 and CVE-2026-123633.
  • ingress-nginx is vulnerable to CVE-2026-123633 and won’t get a patch, so turn off HTTP/2 and plan a move to a maintained ingress or an nginx 1.30.7/1.31.9 build.
  • With Aikido, click "Am I affected?" on the Aikido dashboard to see whether nginx2root hits you.
  • Aikido Images will have patched nginx base images ready, so you can rebuild on a fixed image instead of patching by hand.

Am I affected?

If you use Aikido, click "Am I affected?" on the Aikido home page.

Each of the five is an independent attack path, and they affect different configurations:

CVEAffected configurationFirst affected releaseBlocked by disabling HTTP/2
CVE-2026-123007HTTP/2 enabled and reachable1.9.5Yes
CVE-2026-123634resolver is set, and a proxy_pass uses a variable (e.g. proxy_pass http://$host;)1.13.4No
CVE-2026-123633HTTP/2 with requests forwarded to an upstream (backend) server1.19.7Yes
CVE-2026-121810HTTP/3 (QUIC) with requests forwarded to an upstream (backend) server1.25.0No
CVE-2026-113425Mail proxy using proxy on and auth_http0.5.15No

For CVE-2026-123634 the table shows the tested setup. Other nginx features that create subrequests, such as SSI (Server Side Includes) which lets a page tell nginx to insert content from somewhere else before sending the finished page back, may reach the same bug, so turning off mirror alone does not make a server safe.

If you are using one of these Linux distributions, they ship nginx versions within the reported affected range:

  • Ubuntu 24.04: nginx 1.24.0
  • Ubuntu 22.04: nginx 1.18.0
  • Debian 12: nginx 1.22.1
  • Debian 13: nginx 1.26

These distributions may backport the fix, applying it to their existing nginx package without changing the nginx version number. A patched installation could still report 1.18.0. If you installed nginx through your Linux distro, check your distro's security advisory for this CVE instead of trusting the version number.

How to fix

With Aikido, click "Am I affected?" on the Aikido homepage to see whether nginx2root hits you. Aikido Images will have patched nginx base images ready, so you can rebuild on a fixed image instead of patching by hand.

To fix it yourself:

  1. Update nginx to 1.31.9 (mainline) or 1.30.7 (stable), then restart nginx.
  2. Check your distribution's package version against its security advisory. Distributions often backport fixes without changing the version nginx -v prints.
  3. If you can't update yet, apply the mitigation for your configuration:
    • CVE-2026-123007 and CVE-2026-123633: disable HTTP/2. On nginx 1.25.1 and later, set http2 off; in each affected server block. On older versions, remove http2 from the listen directive.
    • CVE-2026-123634: point proxy_pass at a fixed upstream group (remove request-time DNS).
    • CVE-2026-121810: remove the QUIC listeners and set http3 off;.
    • CVE-2026-113425: bind mail proxy listeners to a loopback address, or allow only trusted IP addresses in your firewall.
  4. After changing the configuration, reload nginx. Restart old nginx workers if any are still running.

For the kernel flaw, hosts that don't use SCTP can add install sctp /bin/false to a .conf file under /etc/modprobe.d/. This does not unload a module that is already loaded or affect SCTP compiled into the kernel.

What is nginx2root

nginx2root is the name given to the five nginx vulnerabilities and the kernel flaw chained with them. Their root causes:

  • CVE-2026-123007: an integer overflow in HTTP/2 flow control that leads to an out-of-bounds write on the heap.
  • CVE-2026-123634: a use-after-free in the DNS resolver when a request and its mirror subrequest wait for the same lookup.
  • CVE-2026-123633: a use-after-free where nginx closes an HTTP/2 connection and frees a request that is still opening an upstream connection.
  • CVE-2026-121810: the same pattern as CVE-2026-123633, on HTTP/3 (QUIC) connections.
  • CVE-2026-113425: a use-after-free in the mail proxy when a client resets the connection during an auth_http lookup.

The kernel flaw is a use-after-free in the SCTP send path, introduced in Linux 4.15 in 2018.

The five nginx vulnerabilities were reported to F5 by Xint researchers (@imssm99, @cdor1, @tjbecker, @yves). Xint says it found CVE-2026-123007 while preparing for ZeroDay Cloud 2026, and the other four in an automated analysis run a few days later.

What is nginx and why it's important

Nginx is software that handles incoming traffic for websites and apps. When you visit a site, your browser often talks to nginx first. Nginx either sends back the page itself or passes your request to the app that builds the response.

With the vulnerabilities, an attacker can send specially crafted messages that cause nginx to damage data inside its own running process. That data helps determine what nginx does next. If the attacker can manipulate it successfully, nginx starts running commands they chose, giving them access to the server instead of just its web pages.

Nginx is widely used, and handling messages from strangers is its everyday job.

Sources: Xint technical write-up, nginx2root.com, CyberSecurityNews (fixed versions)

4.7/5
Tired of false positives?

Try Aikido like 100k others.
Start Now
Get a personalized walkthrough

Trusted by 100k+ teams

Book Now
Scan your app for IDORs and real attack paths

Trusted by 100k+ teams

Start Scanning
See how AI pentests your app

Trusted by 100k+ teams

Start Testing
Authors
Oscar Sanchez
Security researcher
Hunter Schwartz
Security Engineer
Sooraj Shah
Content Marketing Lead
Scan for malware
Secure your code, cloud, and runtime in one central system. Find and fix vulnerabilities fast automatically.
Start for free
Share:

Recently Added

November 17, 2026

Java4Shell: RCE flaw in OpenJDK's Base64 decoder, with affected versions and fix (CVE-2026-114938)

Java4Shell is a flaw in OpenJDK’s Base64 decoder that can let attackers run code remotely, sometimes without authentication. Here are the affected versions, the fixed builds and how to mitigate it today.
Read more
November 17, 2026

Two malicious agent-framework releases hit PyPI in 33 minutes

Two malicious agent-framework releases on PyPI ran a credential stealer on every Python start, targeting Azure, Azure DevOps, and GitHub Actions secrets.
Read more
November 13, 2026

Critical Apache HTTP Server vulnerability can allow remote code execution (CVE-2026-119618)

A critical race condition in Apache HTTP Server’s HTTP/2 module lets a remote attacker run code with no credentials. Upgrade to 2.4.71, or turn off HTTP/2 if you can’t patch yet.
Read more