Executive Summary
CVE-2026-123633 is a use-after-free in the NGINX worker process that is reachable when NGINX is configured for HTTP/2 client connections and proxies requests to a backend, triggered by a crafted request while the worker is low on worker_connections. The defect carries a CVSS score of 8.1 and can produce a worker crash denial-of-service or, on systems with Address Space Layout Randomization disabled or bypassed, remote code execution against the component that often sits directly in front of OT dashboards, historians, and vendor web interfaces.
Technical Exposure Breakdown
The condition exists in the HTTP/2 request handling path during proxying. When the worker process is operating near its connection ceiling, memory associated with a request structure can be freed and then referenced again, giving an attacker a path to corrupt worker memory. The grounding data describes two outcomes: denial-of-service, which is reliably achievable, and code execution, which is gated on ASLR being disabled or defeated. There is no control plane exposure per the source, so the attack surface is the data path that terminates client HTTP/2 connections.
Per the grounding data, affected software spans a wide portion of the F5 NGINX portfolio. NGINX Open Source is listed vulnerable in ranges 1.19.7 through 1.30.7 and 1.31.0 through 1.31.9. NGINX Plus is listed in 37.0.0 through 37.0.7.1 and 37.1.0 through 37.2.0.1. NGINX Ingress Controller is listed in 5.0.0 through 5.8.0 and in the 2026-lts-r1 through 2026-lts-r11 branch. NGINX Gateway Fabric is listed in 1.5.0 through 1.6.2 and 2.0.0 through 2.9.0. NGINX Instance Manager is listed in 2.18.0 through 2.24.0, and several F5 WAF and DoS component ranges are also enumerated. Red Hat products including Enterprise Linux and the 3scale API Management Platform appear in the grounding data without resolved version ranges, so treat those as under evaluation rather than confirmed.
The precondition that matters operationally is HTTP/2 termination with proxying enabled. NGINX deployments that only serve static content without proxying, or that have not enabled HTTP/2 for client connections, present a narrower exposure. Patch status is listed as unknown in the grounding data, so defenders should not assume a fixed build is available in their branch.
OT Impact and Compliance Risk
NGINX is heavily used as a reverse proxy, TLS terminator, and Kubernetes ingress layer in modern OT and converged environments. In these roles it fronts SCADA web HMIs, historian query interfaces, vendor configuration portals, and remote access gateways. A worker crash DoS removes operator visibility into the process. Where ASLR protections are weak, which is common on older or minimally hardened embedded Linux builds and appliance firmware, the code execution outcome puts a pivot point inside the trust boundary that separates IT from the control network.
From a compliance standpoint, an exploitable internet-facing or DMZ NGINX instance implicates IEC 62443 zone and conduit segmentation expectations and NERC CIP electronic security perimeter controls where it sits on an access path to BES Cyber Systems. Water utilities should map this against AWIA 2018 risk and resilience assessments where NGINX fronts remote operations portals. Pipeline operators under TSA SD-02C should treat an exposed proxy as part of their critical cyber system access control scope.
Compensating Controls
Do not rely on a vendor patch alone, and do not run active vulnerability scans against production OT proxies, since probing HTTP/2 edge cases can crash workers and brick dependent services. First, where operationally acceptable, disable HTTP/2 for client connections on NGINX instances that terminate OT-facing traffic, forcing HTTP/1.1 and removing the trigger path. Second, raise worker_connections headroom so workers are far less likely to enter the low-connection state the defect depends on, and monitor connection saturation as an early signal. Third, confirm ASLR is enabled on the host to downgrade the most severe outcome from code execution to DoS. Fourth, place a virtual patch in front of the proxy. A Suricata rule concept: inspect HTTP/2 traffic for anomalous stream creation and reset floods, and alert on bursts of connection resets correlated with worker restarts, which are consistent with attempts to drive the connection pool low before delivering the malformed request. Enforce strict source allow-listing so only known management stations reach OT-facing NGINX endpoints.
BreachSpider Intel
BreachSpider tracks CVE-2026-123633 and related NGINX edge exposure across the 384,000+ CVE corpus and 165,000+ catalog products so OT teams can monitor affected branches without active scanning.
