Executive Summary

CVE-2026-123634 is a use-after-free condition triggered when NGINX Plus or NGINX Open Source acts as a proxy with a variable-based proxied server name and an SSI or mirror directive issues a subrequest to a location resolving the same server name, allowing a crafted HTTP request to corrupt worker process memory. In OT contexts where NGINX fronts HMIs, historian dashboards, remote access portals, or Kubernetes workloads near the control boundary, the practical result is worker crashes and, where ASLR is disabled or bypassed, remote code execution on a device sitting at the edge of the process network.

Technical Exposure Breakdown

The vulnerable component is the NGINX request processing path for subrequests. Three conditions must hold at once: the instance is configured as a proxy, the proxy_pass or equivalent upstream server name is constructed with variables, and an SSI or mirror directive generates a subrequest that resolves back to the same server name. This specific combination triggers a use-after-free in the worker process. The attack vector is a single specially crafted HTTP request, which means no authentication or prior session state is required if the vulnerable configuration is externally reachable.

Per the grounding data, the issue spans a wide software family. NGINX Open Source is affected across 0.6.18-0.8.55, 1.0.0-1.30.7, and 1.31.0-1.31.9. NGINX Plus ranges include 37.0.0-37.0.8.1 and 37.1.0-37.3.0.1. The blast radius extends into orchestration tooling: NGINX Ingress Controller 5.0.0-5.8.0 and 2026-lts-r1 through 2026-lts-r11, NGINX Gateway Fabric 1.5.0-1.6.2 and 2.0.0-2.9.0, and NGINX Instance Manager 2.19.0-2.25.0. Related WAF ranges include 4.12.0-4.16.0, 5.4.0-5.8.0, 5.9.0-5.14.4, and 5.16.0-5.16.2. The CVSS score is 8.1. This is not flagged in the known exploited vulnerability catalog at time of writing. Patch status in the grounding data is listed as unknown, so treat fixed-version claims with skepticism until the vendor advisory confirms specific builds.

OT Impact and Compliance Risk

NGINX rarely runs on the PLC itself, but it is common in the DMZ and in the convergence layer: reverse proxies for vendor remote access, web gateways for SCADA visualization, and ingress controllers for containerized data acquisition or analytics running adjacent to Level 3 systems. A worker crash is a denial-of-service against operator visibility. Code execution on that proxy is a pivot point into the historian, the engineering workstation subnet, or the ingress mesh that routes to control applications.

Under IEC 62443, this challenges zone and conduit segmentation (SR 5.1) and the integrity of the conduit terminating the proxy. For NERC CIP registered entities, an internet-facing or EACMS-classified proxy in scope implicates CIP-005 electronic access controls and CIP-007 patch management timelines. Pipeline operators under TSA SD-02C should treat any affected proxy in the critical cyber system boundary as requiring documented mitigation. Water and wastewater utilities assessing risk under AWIA 2018 obligations should inventory NGINX in their remote access and monitoring stack.

Compensating Controls

Do not assume a vendor patch is immediately deployable. These proxies often sit in change-controlled zones with maintenance windows measured in months. First, inspect configurations for the specific trigger: a variable-based upstream server name combined with any ssi on; block or mirror directive. Removing or rewriting either breaks the required condition and is the cleanest short-term mitigation. Where SSI is not operationally required, disable it. Confirm ASLR is enabled on every host running NGINX to force the attacker into a crash-only outcome rather than code execution.

For virtual patching, place a filtering layer upstream of the vulnerable proxy. A Suricata rule concept: inspect HTTP requests for patterns that would drive a mirror or SSI subrequest loop back to the same variable-resolved upstream, and alert on anomalous subrequest recursion toward internal server names. Rate-limit and geofence any externally reachable proxy. Do not run active vulnerability scans against production control-adjacent NGINX instances without a bench validation first, since aggressive probing of these configurations can crash the exact worker processes you are trying to protect.

BreachSpider Intel

BreachSpider tracks CVE-2026-123634 and the wider NGINX proxy exposure across OT-adjacent deployments, and monitoring is available through BreachSpider for operators needing continuous visibility into affected product ranges.