Executive Summary
CVE-2026-123007 allows an attacker to drive the NGINX HTTP/2 flow control window beyond its allowed threshold, producing a heap buffer overflow that typically terminates the worker process with a segmentation fault and, on hosts with ASLR disabled or bypassable, can lead to remote code execution. In OT environments where NGINX fronts HMI portals, historian dashboards, remote access gateways, or Kubernetes ingress for containerized SCADA components, a crash of the worker process means loss of operator visibility and, in the RCE case, a foothold adjacent to control traffic.
Technical Exposure Breakdown
The defect sits in NGINX HTTP/2 request handling. When the server processes certain traffic patterns, the flow control window accounting fails to enforce its ceiling, allowing a write past the bounds of a heap allocation. The direct consequence is memory corruption of the NGINX worker. The most common observable outcome is a segmentation fault and worker restart. The more severe outcome is code execution, which the source conditions on ASLR being disabled or an attacker being able to bypass ASLR. That condition matters. Many embedded and appliance-grade Linux builds used in field equipment ship with weakened or disabled ASLR for performance or determinism reasons, which moves this CVE from a denial of service into a potential remote execution primitive on exactly the kind of hardware OT operators deploy at the edge.
The affected surface is wide. Per the grounding data, NGINX Open Source is affected across 1.9.5 through 1.30.7 and 1.31.0 through 1.31.9. NGINX Plus is affected in 37.0.0 through 37.0.8.1 and 37.1.0 through 37.3.0.1. The container and orchestration tier is also in scope: NGINX Ingress Controller 5.0.0 through 5.8.0 and the 2026-LTS-R1 through 2026-LTS-R11 line, NGINX Gateway Fabric 1.5.0 through 1.6.2 and 2.0.0 through 2.9.0, NGINX Instance Manager 2.19.0 through 2.25.0, plus the F5 WAF and DoS modules across several ranges. Red Hat lists Enterprise Linux and several image products as impacted. The attack vector is network reachable and requires no authentication to attempt a crash, which is the baseline risk even where code execution is not achievable. CVSS is scored at 8.1.
OT Impact and Compliance Risk
NGINX rarely sits inside the deterministic control loop, but it very often sits one layer out, terminating TLS for operator web interfaces, proxying vendor remote support sessions, or acting as ingress for containerized applications in a converged plant network. A worker crash removes the operator interface during the window it takes to restart, and a looping crash from sustained malicious traffic is a sustained visibility outage. Under IEC 62443, loss of an interface in a higher security zone that fronts control assets is a zone boundary failure and should be evaluated against the zone and conduit model. For electric utilities, any such proxy operating as an Electronic Access Point or supporting Interactive Remote Access falls under NERC CIP-005 and CIP-007 patch management and access control obligations. Pipeline operators under TSA SD-02C and water systems under AWIA 2018 should treat an internet-reachable or DMZ-reachable NGINX instance as an in-scope cyber asset requiring documented mitigation.
Compensating Controls
Do not rely on a patch cycle alone, and do not run an active vulnerability scanner against field-deployed NGINX appliances, since malformed HTTP/2 probes against a vulnerable worker can trigger the very crash you are testing for and brick an operator interface mid-shift. Passive inventory and configuration review are the safe path to identify affected versions. For immediate reduction, disable HTTP/2 on any NGINX instance that does not strictly require it by removing http2 from the listen directive; this eliminates the vulnerable code path. Confirm ASLR is enabled on the host where NGINX runs to downgrade the RCE condition toward denial of service. Place a virtual patch in front of the affected service: a Suricata rule concept is to alert and drop on anomalous HTTP/2 WINDOW_UPDATE frame sequences and on connections where the cumulative flow control window increment exceeds protocol-reasonable bounds, enforced at an inline sensor on the conduit between the enterprise and OT zones. Rate limit HTTP/2 connections per source and terminate HTTP/2 upstream of the NGINX worker where an intermediary proxy can normalize framing.
BreachSpider tracks CVE-2026-123007 exposure across the 165,000+ catalog products and the 10,000+ CVEs linked to industrial automation vendors, and monitors for exploitation signals relevant to OT-fronting NGINX deployments.
