
PEACH
Un framework di isolamento del tenant
CVE-2026-123634 is a use-after-free vulnerability in F5 NGINX Plus and NGINX Open Source that can allow unauthenticated remote attackers to crash worker processes, corrupt memory, or achieve remote code execution (RCE). It is part of a broader set of NGINX vulnerabilities collectively dubbed "nginx2root" disclosed on November 18, 2026. Affected versions include NGINX Open Source 0.6.18 through 1.30.x before 1.30.7 and 1.31.x before 1.31.9, and NGINX Plus R33, 37.0.x before 37.0.8.1, and 37.1.x before 37.3.0.1. The vulnerability carries a CVSS v3.1 base score of 8.1 (High) and a CVSS v4.0 base score of 9.2 (Critical) (GitHub Advisory, Red Hat Bugzilla).
The vulnerability is classified as CWE-416 (Use After Free) and CWE-825 (Expired Pointer Dereference). It is triggered under a specific configuration: NGINX must be acting as a proxy where the proxied server name contains variables, and either a Server Side Includes (SSI) or mirror directive issues a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request can cause a worker process to reference freed memory. RCE is possible if ASLR is disabled on the host or if an attacker can bypass ASLR; otherwise, the most likely outcome is a worker process crash or memory corruption (GitHub Advisory, Red Hat Bugzilla).
Successful exploitation can result in a crash of the NGINX worker process (denial of service), corruption of worker memory, or full remote code execution on the affected server. Because NGINX is widely deployed as a reverse proxy and load balancer, exploitation could expose proxied backend services, sensitive configuration data, and credentials to an attacker. In scenarios where RCE is achieved, lateral movement to backend systems or privilege escalation to root (as suggested by the "nginx2root" campaign name) is a realistic follow-on risk (GitHub Advisory, F5 Advisory).
As of the disclosure date (November 18, 2026), there is no public proof-of-concept exploit and no confirmed in-the-wild exploitation (Feedly). The EPSS score is 0.0, reflecting low current exploitation probability. The vulnerability is not listed in the CISA KEV catalog at this time. Exploitation requires high attack complexity due to the specific NGINX configuration prerequisites (proxy with variable server names and SSI/mirror directives), and ASLR bypass is needed for reliable RCE. The vulnerability is not automatable per NVD SSVC assessment, though the technical impact is rated "total" (Feedly).
proxy_pass directive using a variable in the server name (e.g., proxy_pass http://$host), and that SSI (ssi on) or a mirror directive is active in a location block that resolves the same server name./var/log/nginx/error.log or journalctl); entries such as worker process XXXX exited on signal 11 (SIGSEGV) or worker process XXXX exited on signal 6 (SIGABRT) may indicate memory corruption triggered by exploitation attempts.Host header or request URI contains crafted values designed to manipulate variable-based server name resolution; unexpected outbound connections from the NGINX worker process to attacker-controlled IPs following a crash-and-restart cycle./bin/sh, curl, wget) if RCE is achieved; NGINX worker processes restarting at an abnormal frequency.F5 has released patched versions: NGINX Open Source 1.30.7 (for the 1.30 branch) and 1.31.9 (for the 1.31 branch); NGINX Plus 37.0.8.1 (for the R37.0 branch) and 37.3.0.1 (for the R37.1+ branch). Upgrading to a patched version is the primary recommended remediation (F5 Advisory, GitHub Advisory). As a configuration-based workaround, administrators should audit NGINX proxy configurations and avoid using variables in proxy_pass server names when combined with SSI or mirror directives. Additionally, ensuring ASLR is enabled on the host OS limits the exploitability to DoS rather than RCE. Network-level access controls restricting HTTP traffic to trusted sources can further reduce exposure.
The "nginx2root" disclosure generated significant community attention given NGINX's ubiquity as a web server and reverse proxy. Multiple security vendors and researchers published analyses, including Wiz, watchTowr, Aikido Security, Semgrep, Sophos, and CERT-EU, all emphasizing the critical nature of the vulnerability cluster and urging immediate patching (watchTowr, Wiz Blog, Sophos Advisory). CERT-EU issued security advisory 2026-022, and national CERTs including Ireland's NCSC published guidance. Social media discussion on X (Twitter) and security forums was active, with researchers noting the broad attack surface given NGINX's estimated deployment on hundreds of millions of servers. AlmaLinux and other Linux distributions published their own response blogs, and downstream projects such as BTCPay Server and DDEV issued emergency update notices.
Disponibilità delle patch per le principali distribuzioni Linux e relative versioni.
bookworm
nginx: 1.22.1-9+deb12u11
sid
nginx: 1.30.6-4
trixie
nginx: 1.26.3-3+deb13u11
bionic (esm-infra)
nginx: 1.14.0-0ubuntu1.11+esm6
devel
nginx: 1.30.6-3ubuntu2
focal (esm-infra)
nginx: 1.18.0-0ubuntu1.7+esm5
jammy
nginx: 1.18.0-6ubuntu14.23
noble
nginx: 1.24.0-2ubuntu7.20
resolute
nginx: 1.28.3-2ubuntu1.13
trusty (esm-infra-legacy)
nginx: 1.4.6-1ubuntu3.9+esm10
xenial (esm-infra-legacy)
nginx: 1.10.3-0ubuntu0.16.04.5+esm11
RHEL 9
:appstream:nginx-0:1.20.1-14.el9_2.8.src
RHEL 10
nginx-0:1.26.3-1.el10_0.10.src
Fonte: Questo report è stato generato tramite IA
Valutazione gratuita delle vulnerabilità
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 una demo personalizzata
"La migliore esperienza utente che abbia mai visto offre piena visibilità ai carichi di lavoro cloud."
"Wiz fornisce un unico pannello di controllo per vedere cosa sta succedendo nei nostri ambienti cloud."
"Sappiamo che se Wiz identifica qualcosa come critico, in realtà lo è."