> ## Documentation Index
> Fetch the complete documentation index at: https://blog.onetsolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# nginx2root (CVE-2026-123007): critical nginx HTTP/2 RCE

> nginx2root (CVE-2026-123007) lets attackers run code on nginx servers with HTTP/2, public PoC. Fixed versions, distro packages and how to disable HTTP/2.

*Published on November 20, 2026*

> [!WARNING]
>
> **CVE-2026-123007 — nginx, HTTP/2 module.** An unauthenticated attacker can corrupt the memory of an nginx worker and run code in it, on any server that accepts HTTP/2. A public exploit exists. nginx **1.30.7** (stable) and **1.31.9** (mainline), released on November 18, 2026, fix the flaw. If your nginx serves HTTP/2, update today or disable HTTP/2 in the meantime.

## The bug in two sentences

In HTTP/2 flow control, queued data is credited back to the connection's send window twice: once by a `WINDOW_UPDATE`, once by stream cleanup after a `RST_STREAM`. The window then exceeds its allowed limit, an integer underflow (CWE-191) yields a negative length, and a huge memory copy writes past the buffer: the attacker hijacks a function pointer and runs commands with the privileges of the nginx worker.

The flaw was found by xint.io, who named it **nginx2root**. The name comes from the chain they describe: the nginx worker first, then root through a separate Linux kernel flaw in SCTP, whose details are not public yet.

Affected versions:

* **nginx 1.9.5 through 1.30.6**, fixed in **1.30.7** (stable branch);
* **nginx 1.31.0 through 1.31.8**, fixed in **1.31.9** (mainline branch).

The bug dates back to the arrival of HTTP/2 in nginx 1.9.5, in 2015.

F5, the vendor behind nginx, scores the flaw **8.1** in CVSS 3.1 (`AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) and **9.2** in CVSS 4.0. The NVD entry carries the same scores. Red Hat rates it "Critical", Ubuntu high priority.

> [!NOTE]
>
> Rapid7 has published a proof of concept that achieves unauthenticated remote code execution against nginx 1.31.8 with HTTP/2 and TLS. The flaw is not in CISA's KEV catalog (November 20, 2026 version), and no active exploitation is reported. The same update fixes at least eight other nginx CVEs.

## Sizing your exposure

The question to ask: **does your nginx accept HTTP/2?** Red Hat states that exploitation requires a server that accepts HTTP/2 connections. An nginx that only serves HTTP/1.1 is not exposed to this CVE.

| Profile | Exposure | Action |
| - | - | - |
| nginx with HTTP/2 enabled, reachable from the Internet | **Critical**: public exploit, no authentication | Update today; if you can't, disable HTTP/2 in the meantime |
| nginx with HTTP/2 enabled, internal access only | High | Update promptly |
| nginx serving HTTP/1.1 only | Not exposed to this CVE | Update anyway: the release fixes other flaws |
| gRPC frontend (`grpc_pass`) | **Critical**: HTTP/2 cannot be turned off | Update today |
| Kubernetes, community `ingress-nginx` controller | **Critical**: HTTP/2 on by default, no fix planned | Set `use-http2` to `"false"`, plan a migration |
| Kubernetes, F5 NGINX Ingress Controller | Depends on the version | Move to 5.8.0 |

To check whether HTTP/2 is on, read the loaded configuration:

```bash theme={null}
# Version and build options (HTTP/2 module)
nginx -v
nginx -V 2>&1 | tr ' ' '\n' | grep http_v2

# Full effective configuration: listen ... http2 and http2 on directives
sudo nginx -T 2>/dev/null | grep -nE 'http2'
```

A `listen ... http2` directive or an `http2 on;` line means HTTP/2 is enabled on that port.

> [!NOTE]
>
> Don't rely on the version printed by `nginx -v` alone. Debian, Ubuntu and AlmaLinux backport the fix without changing the upstream version: Ubuntu 24.04 still reports nginx 1.24.0 once patched. Only the full package version, compared with your distribution's advisory, is the reference.

## Updating nginx, distro by distro

The real fix is a package update followed by a **restart** of nginx: a plain `reload` keeps the old workers running for as long as they serve connections.

Take a [snapshot of your VPS](https://help.onetsolutions.net/vps/snapshot) first.

### Debian

| Version | Fixed `nginx` package | Advisory |
| - | - | - |
| Debian 13 (trixie) | `1.26.3-3+deb13u11` | DSA-6642-1 |
| Debian 12 (bookworm) | `1.22.1-9+deb12u11` | DLA-4918-1 |
| Debian unstable (sid) | `1.30.6-4` | — |

### Ubuntu

| Version | Fixed `nginx` package |
| - | - |
| 26.10 | `1.30.4-7ubuntu1.2` |
| 26.04 LTS | `1.28.3-2ubuntu1.13` |
| 24.04 LTS | `1.24.0-2ubuntu7.20` |
| 22.04 LTS | `1.18.0-6ubuntu14.23` |
| 20.04 LTS | `1.18.0-0ubuntu1.7+esm5` (Ubuntu Pro) |

Advisory: USN-9159-1, November 19, 2026.

```bash theme={null}
# Debian, Ubuntu: install the fixes (nginx and its modules), then restart
sudo apt update
sudo apt upgrade
sudo systemctl restart nginx

# Check the installed version
dpkg -l nginx | grep ^ii
```

### RHEL and AlmaLinux

Red Hat lists RHEL 8 (the `nginx:1.24` stream), RHEL 9 and RHEL 10 as affected. As of November 20, 2026, its bulletin RHSB-2026-019 says fixes are on the way, with no erratum released yet: follow the [Red Hat CVE page](https://access.redhat.com/security/cve/cve-2026-123007).

AlmaLinux shipped its fixes on November 18, 2026:

| Version | Fixed `nginx` package | Advisory |
| - | - | - |
| AlmaLinux 10 | `2:1.26.3-16.el10_3.1.alma.2` | ALSA-2026:A024 |
| AlmaLinux 9 (base package) | `2:1.20.1-32.el9_9.1.alma.3` | ALSA-2026:A025 |

For AlmaLinux 8 and the `nginx:1.24` and `nginx:1.26` module streams on AlmaLinux 9, check [errata.almalinux.org](https://errata.almalinux.org).

```bash theme={null}
# Find out whether nginx comes from a module stream
dnf module list --enabled nginx

# Install the fix, then restart
sudo dnf upgrade 'nginx*'
sudo systemctl restart nginx

# Check the installed version
rpm -q nginx
```

### Kubernetes

The community `ingress-nginx` controller is no longer maintained: according to Upwind, every release is affected and none will be fixed. HTTP/2 is on by default. Turn it off in the controller's ConfigMap:

```bash theme={null}
# Adjust the ConfigMap name and namespace to your installation
kubectl -n ingress-nginx patch configmap ingress-nginx-controller \
  --type merge -p '{"data":{"use-http2":"false"}}'
```

Then plan a move to a maintained controller. F5 NGINX Ingress Controller is fixed in **5.8.0**, NGINX Gateway Fabric in **2.9.0**.

## Disabling HTTP/2 until you can update

If you can't update right away, Red Hat and xint.io recommend disabling HTTP/2. Clients fall back to HTTP/1.1 on their own.

Remove the `http2` parameter from **every** `listen` directive:

```nginx theme={null}
# Before
listen 443 ssl http2;
listen [::]:443 ssl http2;

# After
listen 443 ssl;
listen [::]:443 ssl;
```

Since nginx 1.25.1 (Debian 13, Ubuntu 26.04, AlmaLinux 10), HTTP/2 can also be turned on with a dedicated directive. Replace every `http2 on;` with:

```nginx theme={null}
http2 off;
```

Test the configuration, then restart:

```bash theme={null}
sudo nginx -t && sudo systemctl restart nginx
```

> [!NOTE]
>
> A gRPC frontend cannot do without HTTP/2: `grpc_pass` needs it. There, only the update protects you. Disabling HTTP/2 covers CVE-2026-123007 and CVE-2026-123633; the other flaws in the release, including the mail proxy one (CVE-2026-113425), need the update.

### Blocking SCTP until the kernel fix

xint.io reaches root by chaining the nginx flaw with a flaw in the kernel's SCTP module. Until a fixed kernel ships, they recommend preventing the module from loading:

```bash theme={null}
# Prevent the sctp module from loading
echo 'install sctp /bin/false' | sudo tee /etc/modprobe.d/nginx2root-sctp.conf

# Check it is not already loaded (no output expected)
lsmod | grep sctp
```

This rule does not unload a module that is already loaded, and does not disable SCTP built into the kernel.

## Checking the mitigation

```bash theme={null}
# The package version must match your distribution's advisory
dpkg -l nginx | grep ^ii          # Debian, Ubuntu
rpm -q nginx                      # RHEL, AlmaLinux

# nginx must have restarted after the package update
systemctl show -p ActiveEnterTimestamp nginx
```

If you disabled HTTP/2, check that it is no longer negotiated:

```bash theme={null}
# Prints 1.1 if HTTP/2 is off, 2 if it is still on
curl -sk --http2 -o /dev/null -w '%{http_version}\n' https://localhost/
```

Run the `grep` from "Sizing your exposure" again too: no `listen` directive should carry `http2`, and no `http2 on;` line should remain.

## Re-enabling HTTP/2 after the update

Once the fixed package is installed and nginx restarted, bring HTTP/2 back:

```nginx theme={null}
# nginx 1.25.1 and later
http2 on;

# Older versions
listen 443 ssl http2;
```

```bash theme={null}
sudo nginx -t && sudo systemctl restart nginx
```

On Kubernetes, keep `use-http2` at `"false"` for as long as the community `ingress-nginx` controller is in place.

## What next?

Disabling HTTP/2 is only a stopgap: the target remains your distribution's fixed package. Turn on [automatic security updates](https://blog.onetsolutions.net/en/automatic-security-updates-linux-vps.md) and go through the [nginx audit and hardening routine](https://blog.onetsolutions.net/en/audit-and-harden-nginx-on-a-vps.md). For a related flaw on the Apache side, read [Apache HTTP/2 (CVE-2026-119618)](https://blog.onetsolutions.net/en/apache-http2-cve-2026-119618.md). For any technical question, open a ticket from your [OnetSolutions customer area](https://help.onetsolutions.net/console/support).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.