When NGINX Plus or NGINX Open Source is configured with the ngx_stream_ssl_preread_module module, a specially crafted ClientHello message from an unauthenticated attacker causes forged values of the ngx_stream_ssl_preread_module variables, affecting virtual server selection. In addition, it may also cause a disagreement with a proxied server terminating the SSL/TLS connection without Transport Layer Security (TLS) 1.3 support.
Impact
This vulnerability may allow an attacker to forge values of the ngx_stream_ssl_preread_module variables and bypass the NGINX systems stream routing segmentation. As a result, the attacker may be able to route the connection to a privileged or internal backend that should be unreachable and gain access to sensitive information. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
Disable the ssl_preread directive in favor of SSL/TLS termination on NGINX. For more information, refer to https://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html For example, the following configuration includes the ssl_preread on; directive: stream { log_format sni "PREREAD_SNI=[$ssl_preread_server_name] -> [$backend]"; access_log /var/log/nginx/stream.log sni; map $ssl_preread_server_name $backend { internal.test 127.0.0.1:9002; # privileged backend default 127.0.0.1:9001; # public backend } server { listen 9443; ssl_preread on; proxy_pass $backend; } } To mitigate the issue for this configuration, make the following changes: * Remove the ssl_preread directive. * Terminate TLS on NGINX by adding the following: * Change the listener to ssl. * Configure a certificate and key. * Replacing $ssl_preread_server_name with $ssl_server_name to use SNI-based routing. stream { log_format sni "TLS_SNI=[$ssl_server_name] -> [$backend]"; access_log /var/log/nginx/stream.log sni; map $ssl_server_name $backend { internal.test 127.0.0.1:9002; # privileged backend default 127.0.0.1:9001; # public backend } server { listen 9443 ssl; ssl_certificate /etc/nginx/ssl/fullchain.pem; ssl_certificate_key /etc/nginx/ssl/privkey.pem; ssl_protocols TLSv1.2 TLSv1.3; # ssl_preread removed; NGINX terminates client TLS. proxy_pass $backend; # Use these if the backends still expect TLS. proxy_ssl on; proxy_ssl_server_name on; proxy_ssl_name $ssl_server_name; } } After making the configuration changes, validate the configuration and reload, using the following commands: nginx -t nginx -s reload
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4918-1 | nginx security update |
Ubuntu USN |
USN-9159-1 | nginx vulnerabilities |
Thu, 19 Nov 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:f5:nginx_ingress_controller:2026:r10:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r1:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r2:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r3:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r4:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r5:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r6:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r7:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r8:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r9:*:*:*:lts:*:* |
cpe:2.3:a:f5:nginx_ingress_controller:*:*:*:*:continuous_releases:*:*:* cpe:2.3:a:f5:nginx_ingress_controller:*:*:*:*:long-term_support:*:*:* |
Thu, 19 Nov 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
F5 dos
F5 nginx Gateway Fabric F5 nginx Ingress Controller F5 nginx Instance Manager F5 waf |
|
| CPEs | cpe:2.3:a:f5:dos:*:*:*:*:*:nginx:*:* cpe:2.3:a:f5:nginx_gateway_fabric:*:*:*:*:*:*:*:* cpe:2.3:a:f5:nginx_ingress_controller:*:*:*:*:*:*:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r10:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r1:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r2:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r3:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r4:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r5:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r6:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r7:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r8:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_ingress_controller:2026:r9:*:*:*:lts:*:* cpe:2.3:a:f5:nginx_instance_manager:*:*:*:*:*:*:*:* cpe:2.3:a:f5:nginx_open_source:*:*:*:*:*:*:*:* cpe:2.3:a:f5:nginx_plus:*:*:*:*:*:*:*:* cpe:2.3:a:f5:nginx_plus:37.1.0:*:*:*:*:*:*:* cpe:2.3:a:f5:nginx_plus:r34:*:*:*:*:*:*:* cpe:2.3:a:f5:nginx_plus:r35:*:*:*:*:*:*:* cpe:2.3:a:f5:nginx_plus:r36:*:*:*:*:*:*:* cpe:2.3:a:f5:waf:*:*:*:*:*:nginx:*:* |
|
| Vendors & Products |
F5 dos
F5 nginx Gateway Fabric F5 nginx Ingress Controller F5 nginx Instance Manager F5 waf |
Thu, 19 Nov 2026 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 19 Nov 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-1286 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Wed, 18 Nov 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
F5
F5 nginx Open Source F5 nginx Plus |
|
| Vendors & Products |
F5
F5 nginx Open Source F5 nginx Plus |
Wed, 18 Nov 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Description When NGINX Plus or NGINX Open Source is configured with the ngx_stream_ssl_preread_module module, a specially crafted ClientHello message from an unauthenticated attacker causes forged values of the ngx_stream_ssl_preread_module variables, affecting virtual server selection. In addition, it may also cause a disagreement with a proxied server terminating the SSL/TLS connection without Transport Layer Security (TLS) 1.3 support. Impact This vulnerability may allow an attacker to forge values of the ngx_stream_ssl_preread_module variables and bypass the NGINX systems stream routing segmentation. As a result, the attacker may be able to route the connection to a privileged or internal backend that should be unreachable and gain access to sensitive information. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. | |
| Title | NGINX ngx_stream_ssl_preread_module vulnerability | |
| Weaknesses | CWE-1289 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: f5
Published:
Updated: 2026-11-18T16:51:01.723Z
Reserved: 2026-11-09T18:42:53.901Z
Link: CVE-2026-123640
Updated: 2026-11-18T16:44:14.792Z
Status : Analyzed
Published: 2026-11-18T16:18:04.677
Modified: 2026-11-19T19:43:50.543
Link: CVE-2026-123640
OpenCVE Enrichment
Updated: 2026-11-19T14:00:05Z
Debian DLA
Ubuntu USN