CVE-2026-123633: 
NGINX analisi e mitigazione delle vulnerabilità

Panoramica

CVE-2026-123633 is a use-after-free (UAF) vulnerability in NGINX Plus and NGINX Open Source affecting the HTTP/2 processing stack, dubbed nginx2root by the security community. When NGINX is configured to use HTTP/2 for client connections and proxy those requests to a backend, a specially crafted request can trigger a UAF condition in the worker process when it is running low on worker_connections. On systems where ASLR is disabled or can be bypassed, this may escalate to remote code execution. Affected versions include NGINX Open Source 1.30.0–1.30.6, 1.31.0–1.31.8, and 1.19.7; and NGINX Plus R33, 37.0.0–37.0.7, and 37.1.0–37.2.0. The vulnerability was published on November 18, 2026, with a CVSS v3.1 score of 8.1 (High) and a CVSS v4.0 score of 9.2 (Critical) (GitHub Advisory, Feedly).

Dettagli tecnici

The root cause is classified as CWE-416 (Use After Free) and CWE-825 (Expired Pointer Dereference). When the NGINX worker process is running low on available worker_connections and HTTP/2 is enabled for client-facing connections with proxying to a backend, a specially crafted HTTP/2 request — such as one involving rapid stream resets (RST_STREAM) followed by abrupt TCP connection teardown — can cause the worker to reference freed memory. The vulnerability is a data-plane-only issue with no control-plane exposure. Code execution is conditional on ASLR being disabled or bypassable on the target system; otherwise, the primary impact is denial of service via worker process crash. Public PoC code (Python) demonstrates the DoS vector by flooding NGINX with HTTP/2 RST waves over TLS connections negotiated via ALPN h2, targeting a /slow endpoint to exhaust worker connections and trigger the UAF (GitHub Advisory, Feedly).

Impatto

Successful exploitation can result in a denial-of-service condition by crashing the NGINX worker process, disrupting all traffic handled by that worker. On systems where ASLR is disabled or can be bypassed, an unauthenticated remote attacker may achieve arbitrary code execution with the privileges of the NGINX worker process, potentially gaining access to proxied backend connections, in-flight traffic, and sensitive configuration data. If the NGINX worker runs with elevated privileges, successful RCE could enable lateral movement to backend systems or privilege escalation to root, as suggested by the "nginx2root" moniker used by the research community (GitHub Advisory, Wiz Blog, Feedly).

Sfruttabilità

Multiple public proof-of-concept exploits are available on GitHub, including a Python-based DoS PoC (poc.py) by LLCForge that demonstrates worker crashes via HTTP/2 RST flooding, and a separate repository (Ghost-Bx1/nginx-exploits) claiming a full RCE exploit, though the latter's code was not independently verified (Feedly). A detection/audit script is also publicly available. As of the disclosure date, there is no confirmed evidence of in-the-wild exploitation, and the EPSS score is 0.0; the vulnerability has not been added to the CISA KEV catalog. Exploitation requires no authentication and no user interaction, but does require the worker to be low on worker_connections and, for RCE, ASLR to be disabled or bypassable — conditions that increase attack complexity (Feedly).

Fasi di sfruttamento

  1. Reconnaissance: Identify internet-facing NGINX instances with HTTP/2 enabled using tools like Shodan (ssl:nginx http2) or Censys, targeting versions in the affected ranges (Open Source 1.30.0–1.30.6, 1.31.0–1.31.8, 1.19.7; Plus R33, 37.0.x, 37.1.x).
  2. Verify HTTP/2 support: Confirm the target accepts HTTP/2 via ALPN h2 by initiating a TLS handshake and checking the negotiated protocol.
  3. Establish concurrent HTTP/2 connections: Open many simultaneous TLS connections to the target NGINX HTTPS port (default 443 or 8443), negotiating HTTP/2 via ALPN. Send the HTTP/2 client preface, SETTINGS frame, and SETTINGS ACK to complete the handshake.
  4. Issue a request and immediately reset: On each connection, send a HEADERS frame requesting a slow or resource-intensive endpoint (e.g., /slow) on stream 1, then immediately send an RST_STREAM frame with error code CANCEL, followed by closing the TCP socket with SO_LINGER=0 (abortive RST).
  5. Repeat in waves to exhaust worker_connections: Execute multiple waves of this connection churn using a thread pool to maximize concurrency, driving the NGINX worker process to run low on available worker_connections and triggering the use-after-free condition.
  6. Detect worker crash (DoS): Poll a health endpoint (e.g., GET /health HTTP/1.0) between waves; a failure to receive a 200 response indicates the worker process has crashed.
  7. Escalate to RCE (if ASLR disabled): On targets where ASLR is disabled or can be bypassed, craft a more precise HTTP/2 payload exploiting the UAF primitive to achieve controlled memory corruption and execute arbitrary code in the context of the NGINX worker process (Feedly, GitHub Advisory).

Indicatori di compromissione

  • Network: High volumes of concurrent TLS connections to the NGINX HTTPS port negotiating HTTP/2 (h2 via ALPN), each short-lived with immediate RST_STREAM and TCP RST teardown; unusual spikes in connection churn from a single or small set of source IPs.
  • Network: Repeated requests to slow or resource-intensive endpoints (e.g., /slow) followed by immediate connection drops, observable in network flow data.
  • Logs: NGINX access logs showing a high rate of HTTP/2 requests with status 0 or connection reset errors from the same source IP(s); entries in error.log indicating worker process crashes or restarts (e.g., worker process ... exited on signal 11).
  • Logs: NGINX error log entries referencing memory access violations or segmentation faults in the HTTP/2 processing module.
  • Process: Unexpected NGINX worker process restarts (nginx: worker process respawning frequently) observable via process monitoring or system logs (/var/log/syslog, journalctl).
  • File System: Presence of core dump files in the NGINX working directory or /tmp following worker crashes, which may contain memory artifacts useful for forensic analysis (Feedly, GitHub Advisory).

Mitigazione e soluzioni alternative

F5 has released patched versions: NGINX Open Source 1.31.9 and 1.30.7; NGINX Plus 37.2.0.1 and 37.0.7.1. Upgrading to these versions is the primary recommended remediation. For systems that cannot be immediately patched, consider disabling HTTP/2 for client-facing connections (remove http2 from the listen directive), implementing rate limiting on incoming connections, and ensuring ASLR is enabled on the host OS to significantly increase the difficulty of achieving code execution. Versions that have reached End of Technical Support (EoTS) are not evaluated and should be upgraded (GitHub Advisory, F5 Advisory).

Reazioni della comunità

The vulnerability attracted significant attention from the security community under the name nginx2root, with coverage from major vendors and researchers. Wiz published a detailed technical blog post on the HTTP/2 RCE vulnerabilities (Wiz Blog), and watchTowr released an intelligence report and FAQ covering CVE-2026-123633 alongside related CVEs (watchTowr). JFrog Research, Orca Security, Semgrep, Aikido Security, and Upwind all published technical analyses, with several noting the vulnerability was discovered simultaneously by multiple research teams. CERT/EU, NCSC Ireland, and the Canadian Centre for Cyber Security issued advisories. Sophos, Red Hat, Ubuntu, and AlmaLinux published vendor-specific guidance. Social media discussion was widespread on Mastodon, Bluesky, and X, with community members urging immediate patching given NGINX's estimated deployment on over 225 million websites (Feedly, The Register).

Risorse aggiuntive

Stato delle patch per la distribuzione Linux

Disponibilità delle patch per le principali distribuzioni Linux e relative versioni.

Debian

Risolto

bookworm

nginx: 1.22.1-9+deb12u11

Risolto

sid

nginx: 1.30.6-4

Risolto

trixie

nginx: 1.26.3-3+deb13u11

Risolto

Ubuntu

Risolto

bionic (esm-infra)

nginx: 1.14.0-0ubuntu1.11+esm6

Risolto

devel

nginx: 1.30.6-3ubuntu2

Interessato

focal (esm-infra)

nginx: 1.18.0-0ubuntu1.7+esm5

Risolto

jammy

nginx: 1.18.0-6ubuntu14.23

Risolto

noble

nginx: 1.24.0-2ubuntu7.20

Risolto

resolute

nginx: 1.28.3-2ubuntu1.13

Risolto

trusty (esm-infra-legacy)

nginx

Non interessato

xenial (esm-infra-legacy)

nginx: 1.10.3-0ubuntu0.16.04.5+esm11

Risolto

RHEL / CentOS

Risolto

RHEL 9

:appstream:nginx-0:1.20.1-14.el9_2.8.src

Risolto

RHEL 10

nginx-0:1.26.3-1.el10_0.10.src

Risolto

Alpine

Risolto

edge

nginx: 1.30.7-r0

Risolto

v3.21

nginx: 1.26.3-r4

Risolto

v3.22

nginx: 1.28.3-r8

Risolto

v3.23

nginx: 1.28.3-r8

Risolto

Fonte: Questo report è stato generato tramite IA

Vulnerabilità correlate di NGINX:

CVE ID

Gravità

Punteggio

Tecnologie

Nome del componente

Exploit CISA KEV

Dispone di patch

Data di pubblicazione

CVE-2026-123634CRITICAL9.2
  • NGINX logoNGINX
  • nginx:1.26::nginx
NoSìNov 18, 2026
CVE-2026-123633CRITICAL9.2
  • NGINX logoNGINX
  • nginx-mod-stream-geoip-debuginfo
NoSìNov 18, 2026
CVE-2026-123007CRITICAL9.2
  • NGINX logoNGINX
  • openresty
NoSìNov 18, 2026
CVE-2026-125283MEDIUM6.9
  • NGINX logoNGINX
  • nginx:1.24::nginx-filesystem
NoSìNov 18, 2026
CVE-2026-123640MEDIUM6.9
  • NGINX logoNGINX
  • nginx:1.24::nginx-mod-stream
NoSìNov 18, 2026

Valutazione gratuita delle vulnerabilità

Valuta la tua postura di sicurezza del cloud

Valuta le tue pratiche di sicurezza del cloud in 9 domini di sicurezza per stabilire un benchmark del tuo livello di rischio e identificare le lacune nelle tue difese.

Richiedi valutazione

Ulteriori risorse Wiz

Richiedi una demo personalizzata

Pronti a vedere Wiz in azione?

"La migliore esperienza utente che abbia mai visto offre piena visibilità ai carichi di lavoro cloud."
David EstlickCISO (CISO)
"Wiz fornisce un unico pannello di controllo per vedere cosa sta succedendo nei nostri ambienti cloud."
Adam FletcherResponsabile della sicurezza
"Sappiamo che se Wiz identifica qualcosa come critico, in realtà lo è."
Greg PoniatowskiResponsabile della gestione delle minacce e delle vulnerabilità