Vulnerability DatabaseCVE-2026-123634

CVE-2026-123634: 
NGINX vulnerability analysis and mitigation

Overview

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).

Technical details

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).

Impact

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).

Exploitability

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).

Exploitation steps

  1. Reconnaissance: Identify internet-facing NGINX instances running vulnerable versions (Open Source 1.30.0–1.30.6, 1.31.0–1.31.8, or legacy 0.6.18+; Plus R33, 37.0.0–37.0.8, or 37.1.0–37.3.0) using tools like Shodan, Censys, or banner grabbing.
  2. Identify vulnerable configuration: Confirm the target NGINX instance is configured as a proxy with a 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.
  3. Craft malicious HTTP request: Construct a specially crafted HTTP request designed to trigger the subrequest path through the SSI or mirror directive, causing the resolver to free and then re-reference the server name memory in the worker process.
  4. Trigger use-after-free: Send the crafted request to the vulnerable NGINX endpoint. If successful, the worker process will access freed memory, resulting in a crash (DoS) or, under favorable memory layout conditions, controlled memory corruption.
  5. Achieve RCE (if ASLR is disabled or bypassed): If the target system has ASLR disabled or the attacker can leverage an information leak to bypass ASLR, craft the payload to redirect execution flow to attacker-controlled code, achieving RCE as the NGINX worker process user (GitHub Advisory, F5 Advisory).

Indicators of compromise

  • Logs: Repeated NGINX worker process crash/restart entries in system logs (/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.
  • Network: Unusual or malformed HTTP requests targeting proxy endpoints where the 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.
  • Process: Unexpected child processes spawned by the NGINX worker (e.g., /bin/sh, curl, wget) if RCE is achieved; NGINX worker processes restarting at an abnormal frequency.
  • File System: New or modified files in NGINX web root or configuration directories created by the NGINX worker user; presence of web shells or reverse shell scripts in directories writable by the NGINX process (GitHub Advisory, Red Hat Bugzilla).

Mitigation and workarounds

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.

Community reactions

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.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

nginx: 1.22.1-9+deb12u11

Fixed

sid

nginx: 1.30.6-4

Fixed

trixie

nginx: 1.26.3-3+deb13u11

Fixed

Ubuntu

Fixed

bionic (esm-infra)

nginx: 1.14.0-0ubuntu1.11+esm6

Fixed

devel

nginx: 1.30.6-3ubuntu2

Affected

focal (esm-infra)

nginx: 1.18.0-0ubuntu1.7+esm5

Fixed

jammy

nginx: 1.18.0-6ubuntu14.23

Fixed

noble

nginx: 1.24.0-2ubuntu7.20

Fixed

resolute

nginx: 1.28.3-2ubuntu1.13

Fixed

trusty (esm-infra-legacy)

nginx: 1.4.6-1ubuntu3.9+esm10

Fixed

xenial (esm-infra-legacy)

nginx: 1.10.3-0ubuntu0.16.04.5+esm11

Fixed

RHEL / CentOS

Fixed

RHEL 9

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

Fixed

RHEL 10

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

Fixed

Alpine

Fixed

edge

nginx: 1.30.7-r0

Fixed

v3.21

nginx: 1.26.3-r4

Fixed

v3.22

nginx: 1.28.3-r8

Fixed

v3.23

nginx: 1.28.3-r8

Fixed

Source: This report was generated using AI

Related NGINX vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-123634CRITICAL9.2
  • NGINX logoNGINX
  • cpe:2.3:a:openresty:openresty
NoYesNov 18, 2026
CVE-2026-123633CRITICAL9.2
  • NGINX logoNGINX
  • nginx-mod-devel
NoYesNov 18, 2026
CVE-2026-123007CRITICAL9.2
  • NGINX logoNGINX
  • nginx-mod-http-perl
NoYesNov 18, 2026
CVE-2026-125283MEDIUM6.9
  • NGINX logoNGINX
  • nginx:1.14::nginx
NoYesNov 18, 2026
CVE-2026-123640MEDIUM6.9
  • NGINX logoNGINX
  • nginx:1.22::nginx-core
NoYesNov 18, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management