Executive Summary

CVE-2026-120967 allows a remote attacker to bypass client certificate verification when NGINX Plus or NGINX Open Source enforces mutual TLS with ssl_verify_client on inside a non-default stream virtual server. This is a data plane authentication failure with no control plane exposure, and it defeats a certificate boundary that many OT architectures treat as a trusted gatekeeper for protocol proxying.

Technical Exposure Breakdown

The defect is specific to the stream module, not the HTTP module. In OT environments NGINX is frequently deployed as a Layer 4 reverse proxy in front of industrial services that speak raw TCP: historian replication, OPC UA over TCP, MQTT brokers, Modbus gateways fronted by TLS wrappers, and remote access concentrators. The stream module terminates or passes through TLS and, when configured, is supposed to require and validate a client certificate before the backend connection is established.

Per the grounding data, the condition that triggers the bypass is a ssl_verify_client on directive placed in a non-default stream virtual server. A default server is the server block selected when no other block matches the inbound connection. When the certificate check lives in a non-default block, the verification logic can be bypassed, meaning a client presenting no valid certificate, or an untrusted certificate, may still reach the protected backend.

The assigned CVSS score is 4.8. That number understates the operational weight in an OT context because scoring models assume an authentication layer is one of several defenses. In segmented industrial networks, mTLS is often the only strong identity boundary between a jump host zone and a process control zone. When that single boundary fails open, the residual protection is network segmentation alone.

OT Impact and Compliance Risk

If NGINX stream mTLS is your enforcement point for remote vendor access or cross-zone protocol relay, this bypass converts a mutually authenticated channel into an effectively open TCP proxy for anyone who can reach the listener. The physical consequence depends on what sits behind the proxy. A bypass in front of an engineering workstation gateway or an OPC UA server exposes write-capable process interfaces to unauthenticated peers.

Under IEC 62443, this undermines zone and conduit segmentation requirements where mTLS is cited as the conduit authentication mechanism. For NERC CIP registered entities, any NGINX instance acting as an Intermediate System or access control point for Interactive Remote Access would need re-examination against CIP-005 remote access requirements, because the certificate control that was documented as enforced may not be enforced in practice. For pipeline operators under TSA SD-02C, and for water utilities assessing risk under AWIA 2018, the same logic applies anywhere mTLS is the documented identity boundary for remote or cross-segment access.

Compensating Controls

Patch status is listed as unknown in the grounding data, so treat remediation as architectural first and software second.

Once a validated fix is published for your deployed version, apply it in a maintenance window and then re-verify that verification occurs in the default server path, not only in the block you happened to configure.

BreachSpider Intel Footer

BreachSpider tracks CVE-2026-120967 and other data plane authentication failures affecting OT edge proxies, with monitoring available through Intel by BreachSpider.