CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

NGINX HTTP/3 memory corruption with upstream forwarding (nginx2root), fixed in nginx 1.31.9 and 1.30.7

cve · CVE-2026-121810

Coverage
1
first 2026-11-19 → last 2026-11-19
Latest activity
2026-11-19
NGINX nginx2root: five unauthenticated flaws reach worker RCE, Rapid7 PoC public; update 1.31.9, 1.30.7 or…
Peak priority
high
1 high
Targets
technology
sectors: technology
Sources cited
9
9 hosts

Action items (1)

Do-now tasks recorded on the entries about CVE-2026-121810, newest first. Check the date before acting on an older one.

  • Update every internet-facing nginx to 1.31.9 or 1.30.7 (NGINX Plus to 37.3.0.1 or 37.0.8.1) and restart the process, because a reload does not replace the running executable; where the update waits, disable HTTP/2 on exposed listeners, which blocks only CVE-2026-123007 and CVE-2026-123633, since five unauthenticated flaws reach code execution as the worker and Rapid7's proof of concept for one of them is public.
    2026-11-19CVE-2026-123007 +4

Defender insights

What each entry about CVE-2026-121810 tells a defender to do, newest first.

2026-11-19HIGHNGINX nginx2root: five unauthenticated flaws reach worker RCE, Rapid7 PoC public; update 1.31.9, 1.30.7 or Plus 37.3.0.1

Exposure · triage · detection

Story timeline

  1. 2026-11-19NGINX nginx2root: five unauthenticated memory-corruption flaws (CVE-2026-123007 and CVE-2026-123633 in HTTP/2, CVE-2026-121810 in HTTP/3, CVE-2026-123634 in the resolver, CVE-2026-113425 in the mail proxy) can lead to code execution as the worker process; fixed in nginx 1.31.9 and 1.30.7 and NGINX Plus 37.3.0.1 and 37.0.8.1, Rapid7 proof of concept public, no exploitation reported (CVSS 4.0 9.2)
    trending-vulnerabilitiesNGINX nginx2root: five unauthenticated flaws reach worker RCE, Rapid7 PoC public; update 1.31.9, 1.30.7 or Plus 37.3.0.1
ATT&CK techniques (5 across 4 tactics)

5 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application
  • ExecutionCommand and Scripting Interpreter: Unix Shell
  • Privilege EscalationExploitation for Privilege Escalation · Escape to Host
  • ImpactEndpoint Denial of Service: Application or System Exploitation

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-11-19/nginx-nginx2root-five-unauth-memory-corruption-flaws · ATT&CK page ↗

Execution TA0002

T1059.004Command and Scripting Interpreter: Unix Shell×1

Adversaries may abuse Unix shell commands and scripts for execution. Unix shells are the primary command prompt on Linux, macOS, and ESXi systems, though many variations of the Unix shell exist (e.g. sh, ash, bash, zsh, etc.) depending on the specific OS or distribution. Unix shells can control every aspect of a system, with certain commands requiring elevated privileges.

Evidence: 2026-11-19/nginx-nginx2root-five-unauth-memory-corruption-flaws · ATT&CK page ↗

Privilege Escalation TA0004

T1068Exploitation for Privilege Escalation×1

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

Evidence: 2026-11-19/nginx-nginx2root-five-unauth-memory-corruption-flaws · ATT&CK page ↗

T1611Escape to Host×1

Adversaries may break out of a container or virtualized environment to gain access to the underlying host. This can allow an adversary access to other containerized or virtualized resources from the host level or to the host itself. In principle, containerized / virtualized resources should provide a clear separation of application functionality and be isolated from the host environment.

Evidence: 2026-11-19/nginx-nginx2root-five-unauth-memory-corruption-flaws · ATT&CK page ↗

Impact TA0040

T1499.004Endpoint Denial of Service: Application or System Exploitation×1

Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users. Some systems may automatically restart critical applications and services when crashes occur, but they can likely be re-exploited to cause a persistent denial of service (DoS) condition.

Evidence: 2026-11-19/nginx-nginx2root-five-unauth-memory-corruption-flaws · ATT&CK page ↗

Entries about NGINX HTTP/3 memory corruption with upstream forwarding (nginx2root), fixed in nginx 1.31.9 and 1.30.7 (1)

2026-11-19 · view entry permalink →

NGINX nginx2root: five unauthenticated memory-corruption flaws (CVE-2026-123007 and CVE-2026-123633 in HTTP/2, CVE-2026-121810 in HTTP/3, CVE-2026-123634 in the resolver, CVE-2026-113425 in the mail proxy) can lead to code execution as the worker process; fixed in nginx 1.31.9 and 1.30.7 and NGINX Plus 37.3.0.1 and 37.0.8.1, Rapid7 proof of concept public, no exploitation reported (CVSS 4.0 9.2)

F5 and the nginx project published the nginx2root fixes (nginx.org, 2026-11-18); CERT-EU counts five vulnerabilities, all able to lead to unauthenticated code execution with the privileges of the NGINX worker process (CERT-EU, 2026-11-18). CVE-2026-123007 is an HTTP/2 flow-control overflow: cancelling queued response data makes nginx use an invalid length when copying a later response (Rapid7, 2026-11-18), and Wiz demonstrated code execution on nginx serving ordinary static files (Wiz Research, 2026-11-18).

Rapid7 published a working proof of concept for CVE-2026-123007 against nginx 1.31.8; the exploit needs about 128 GB of HTTP/2 traffic and likely fails with concurrent clients (Rapid7, 2026-11-18; Rapid7 repository, 2026-11-18). Rapid7 says execution has the worker's permissions and root is not established; F5, as CERT.at relays it, frames the base effect as worker crashes, with code execution possible where ASLR is disabled or can be bypassed, which Wiz says attackers can do by reading memory first (translated from German) (Rapid7, 2026-11-18; CERT.at, 2026-11-18; Wiz Research, 2026-11-18). CERT-EU reports no exploitation in the wild, NCSC.ch rates exploitation unknown with a proof of concept available, and NCSC-NL expects large-scale exploitation once proof-of-concept code is public (translated from Dutch) (CERT-EU, 2026-11-18; NCSC.ch, 2026-11-18; NCSC-NL, 2026-11-18).

The fixes are in nginx 1.31.9 and 1.30.7 (nginx.org, 2026-11-18). CERT.at lists NGINX Plus 37.3.0.1 and 37.0.8.1 as fixing four of the five (CVE-2026-123007, CVE-2026-121810, CVE-2026-123633 and CVE-2026-113425); it also says 37.2.0.1 and 37.0.7.1 already carry the fix for CVE-2026-123633 but stay affected by CVE-2026-123007 and CVE-2026-121810, and NGINX Plus R33 to R36 have no update (translated from German) (CERT.at, 2026-11-18).

Triage: a large upload is a legitimate cause of an inbound-heavy connection and workers crash for unrelated reasons, so a program started by the worker is the discriminator, not the traffic shape alone (Xint, 2026-11-18).

All five vulnerabilities can lead to unauthenticated code execution with the privileges of the NGINX worker process

no exploitation in the wild has been reported yet

CERT-EU 2026-11-18

Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data.

Rapid7 2026-11-18

Our testing of CVE-2026-123007 demonstrated code execution on NGINX serving ordinary static files, without a backend application or third-party modules.

Wiz Research 2026-11-18

Until then, disabling HTTP/2 on affected listening ports blocks CVE-2026-123007 and CVE-2026-123633. It does not block the other three nginx vulnerabilities.

After installing the update, restart nginx or complete a supported live binary upgrade. A configuration reload alone does not replace the running executable.

Xint 2026-11-18

Builds on: Three configuration-dependent NGINX heap flaws (CVSS 9.2) are fixed in 1.30.6, 1.31.7 and… · CVE-2026-42530 / CVE-2026-42055, NGINX: HTTP/3 QUIC use-after-free and HTTP/2-proxy heap…

vulnerability19 Nov 05:12Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • advisories.ncsc.nl1 (11%)
  • cert.at1 (11%)
  • cert.europa.eu1 (11%)
  • github.com1 (11%)
  • nginx.org1 (11%)
  • rapid7.com1 (11%)
  • security-hub.ncsc.admin.ch1 (11%)
  • wiz.io1 (11%)
  • other1 (11%)