---
title: "NGINX2Root: two critical NGINX flaws, one of them lurking since 2015"
description: "Two critical NGINX flaws could crash a server exposing HTTP/2, or even run code on it, according to Next. Patches have been out since 18 November, and a proof of concept already exists."
canonical: https://inyourgeek.com/en/articles/2026-11-19-nginx2root-deux-failles-critiques-de-nginx-dont-une-datant
type: article
author: "Sébastien Soulier"
publisher: "InYourGeek"
language: en
datePublished: 2026-11-19
dateModified: 2026-11-19
section: "Security"
tags: ["nginx", "faille", "http2", "linux"]
---
# NGINX2Root: two critical NGINX flaws, one of them lurking since 2015
> Two critical NGINX flaws could crash a server exposing HTTP/2, or even run code on it, according to Next. Patches have been out since 18 November, and a proof of concept already exists.
November 19, 2026 · Security · 3 min
According to [Next](https://next.ink/268502/deux-failles-critiques-dans-nginx-reclament-a-leur-tour-une-mise-a-jour-urgente/), which ran the story on 19 November, two critical flaws affect NGINX, and fixes have been available since 18 November. This article rests on that single source, which itself points to the CERT-FR advisory, the post from F5 (the company behind NGINX) and the work of two firms, Xint and Upwind.

## What's affected

The two vulnerabilities, CVE-2026-123007 and CVE-2026-123633, would let an unauthenticated attacker run code on an NGINX server that exposes HTTP/2, provided every condition for exploitation lines up. HTTP/2 isn't on by default, but it is often switched on by hand, Next points out. All current versions are reportedly affected.

The pair belongs to a batch of five code-execution flaws filed under the name "nginx2root", which at least tells you where this is heading. They were reported on 11 October by Xint, a company specialising in security. They score 8.1 on CVSS 3.1 and 9.2 on CVSS 4.0.

What makes this a big deal is how much of the web runs on the thing: in July 2026, Netcraft credited NGINX with 20.4% of all sites and 20% of the million busiest ones. It also sits underneath many Kubernetes ingress controllers and ranks among the most-used Docker images.

## Two distinct mechanisms

The first flaw, CVE-2026-123007, has reportedly been there since 2015. The problem is one of arithmetic: when a client cancels an HTTP/2 stream, NGINX hands back the unused credit without checking the ceiling. If the attacker enlarged their window just beforehand, the counter overshoots the permitted maximum, the value turns negative, and a memory copy in the TLS send path writes out of bounds.

Nobody will mistake this attack for background noise. According to Upwind's figures as relayed by Next, it would take roughly 60 GB of traffic over a single connection to crash a worker process, and 128 GB to reach arbitrary code execution. The catch: the scenario would work in the vast majority of deployments running default settings.

The second, CVE-2026-123633, has reportedly been around since 2021. It's a use-after-free, meaning memory gets used after it has been released. When NGINX runs short of available connections, it closes active ones to claw some back. If it closes an HTTP/2 connection while the connection to the upstream server is being set up, the request is freed while the forwarding code is still using it. An attacker could move into that vacated memory and hijack execution.

## Limited privileges, unless you chain in the kernel

The main limiting factor is NGINX's own architecture: one master process and several worker processes, which run as an unprivileged user. Injected code would run with their rights, so no root access.

Xint nonetheless managed a privilege escalation, using a Linux kernel flaw which, according to Next, hasn't been fixed yet. That chaining isn't part of how the NGINX flaws themselves are rated, but it remains within an attacker's reach.

## What you should do

The fixed versions are 1.31.9 and 1.30.7, released on 18 November. If you can't update right away, you can mitigate the problem by disabling HTTP/2; F5's post gives the commands for whichever version you run.

At the time Next published, the flaws didn't appear to be exploited yet. A proof of concept already exists, however, as noted in particular by the CERT-FR advisory the outlet cites.

One of these bugs got eleven years of peace and quiet before anyone patched it. There's no need for your servers to throw in a bonus week.
## Sources
- [Deux failles critiques dans NGINX réclament à leur tour une mise à jour urgente](https://next.ink/268502/deux-failles-critiques-dans-nginx-reclament-a-leur-tour-une-mise-a-jour-urgente/) — next.ink
_Article written with AI assistance from the cited sources, reviewed and approved by a human before publication._

---

Equivalent HTML page : https://inyourgeek.com/en/articles/2026-11-19-nginx2root-deux-failles-critiques-de-nginx-dont-une-datant
Published by InYourGeek — https://inyourgeek.com/en/a-propos
Method and safeguards : https://inyourgeek.com/en/methode
All articles : https://inyourgeek.com/en/archives
