Skip to content
Threat Brief

← All advisories

CVE-2026-123640

Medium 6.9No known exploitationFix available

NGINX ngx_stream_ssl_preread_module vulnerability

Record last updated

CVSS score

6.9

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 31% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-1289

Patching and mitigation

Patch status
Fix available (source: CVE record (f5))
Fix documented (source date)
Mitigation
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 Source (opens in a new tab)
Vendor guidance
my.f5.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
F5NGINX Open Sourcefrom 1.30.0 before 1.30.71.30.7CVE Program
F5NGINX Open Sourcefrom 1.31.0 before 1.31.91.31.9CVE Program
F5NGINX Open Source1.15.2Not documentedCVE Program
F5NGINX Plusfrom 37.0.0 before 37.0.7.137.0.7.1CVE Program
F5NGINX Plusfrom 37.1.0 before 37.2.0.137.2.0.1CVE Program
F5NGINX PlusR33Not documentedCVE Program
Microsoftazl3 nginx 0.0.0-1 on Azure Linux 3.0Not documented1.30.6-2Microsoft MSRC
f5dosfrom 4.5.0 up to and including 4.7.0Not documentedNIST NVD
f5dosfrom 4.8.0 before 4.13.04.13.0NIST NVD
f5nginx_gateway_fabricfrom 1.5.0 up to and including 1.6.2Not documentedNIST NVD
f5nginx_gateway_fabricfrom 2.0.0 before 2.9.02.9.0NIST NVD
f5nginx_ingress_controllerfrom 2026-lts-r1 before 2026-lts-r112026-lts-r11NIST NVD
f5nginx_ingress_controllerfrom 3.7.1 up to and including 3.7.2Not documentedNIST NVD
f5nginx_ingress_controllerfrom 4.0.0 up to and including 4.0.1Not documentedNIST NVD
f5nginx_ingress_controllerfrom 5.0.0 before 5.8.05.8.0NIST NVD
f5nginx_instance_managerfrom 2.19.0 before 2.25.02.25.0NIST NVD
f5nginx_open_sourcefrom 1.15.2 before 1.30.71.30.7NIST NVD
f5nginx_open_sourcefrom 1.31.0 before 1.31.91.31.9NIST NVD
f5nginx_plusfrom 37.0.0 before 37.0.7.137.0.7.1NIST NVD
f5nginx_plus37.1.0Not documentedNIST NVD
f5nginx_plusr34Not documentedNIST NVD
f5nginx_plusr35Not documentedNIST NVD
f5nginx_plusr36Not documentedNIST NVD
f5waffrom 4.12.0 before 4.16.24.16.2NIST NVD
f5waffrom 5.15.0 before 5.16.25.16.2NIST NVD
f5waffrom 5.4.0 up to and including 5.8.0Not documentedNIST NVD
f5waffrom 5.9.0 before 5.14.45.14.4NIST NVD

Timeline

  1. Disclosure

    CVE record published by f5

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (f5)

    Source: CVE record (f5) (opens in a new tab)

  3. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references