Vulnerability DatabaseCVE-2026-123640

CVE-2026-123640: 
NGINX vulnerability analysis and mitigation

Overview

CVE-2026-123640 is an input validation vulnerability in NGINX's ngx_stream_ssl_preread_module that allows an unauthenticated remote attacker to forge SSL/TLS preread module variables by sending a specially crafted ClientHello message, thereby bypassing stream routing segmentation. It affects NGINX Open Source versions 1.15.2, 1.30.0–1.30.6, and 1.31.0–1.31.8, as well as NGINX Plus R33, 37.0.0–37.0.7, and 37.1.0–37.2.0. The vulnerability was disclosed on November 18, 2026. It carries a CVSS v3.1 base score of 5.3 (Medium) and a CVSS v4.0 base score of 6.9 (Medium) (GitHub Advisory, Red Hat CVE, F5 Advisory).

Technical details

The root cause is improper validation of syntactic correctness and unsafe equivalence in input (CWE-1286, CWE-1289) within the ngx_stream_ssl_preread_module. When NGINX is configured to use this module for TLS stream routing, it inspects the ClientHello message to extract variables such as SNI hostname or protocol version before proxying the connection. An attacker can craft a malformed ClientHello that causes NGINX to derive incorrect values for these preread variables, leading to incorrect virtual server selection. Additionally, the crafted message may cause a TLS handshake disagreement with backend servers that do not support TLS 1.3, potentially disrupting connections. No authentication or special privileges are required; the attack is conducted entirely over the network (GitHub Advisory, Red Hat CVE).

Impact

Successful exploitation allows an unauthenticated attacker to manipulate NGINX stream routing decisions, potentially routing their connection to privileged or internal backend servers that are intended to be unreachable from external networks. This is a data plane issue only — there is no control plane exposure — but the integrity of routing decisions is compromised (low integrity impact), and sensitive information from internal or privileged backend systems may be exposed. Availability is not directly impacted, though TLS handshake disagreements with non-TLS 1.3 backends could cause connection disruptions (GitHub Advisory, F5 Advisory).

Exploitability

As of the disclosure date (November 18, 2026), there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation (Feedly). The EPSS score is 0.0, reflecting a currently low probability of exploitation. The vulnerability is automatable (no user interaction required) and exploitable by unauthenticated network attackers, which lowers the barrier for potential future exploitation. It has not been added to the CISA Known Exploited Vulnerabilities catalog at this time.

Exploitation steps

  1. Reconnaissance: Identify internet-facing NGINX instances configured with ngx_stream_ssl_preread_module using tools like Shodan or Censys, targeting version ranges 1.30.0–1.30.6, 1.31.0–1.31.8 (Open Source) or R33, 37.0.0–37.0.7, 37.1.0–37.2.0 (Plus).
  2. Craft malicious ClientHello: Construct a specially crafted TLS ClientHello message that contains malformed or manipulated fields (e.g., SNI extension, supported versions) designed to cause NGINX's ngx_stream_ssl_preread_module to derive incorrect variable values.
  3. Send crafted message: Initiate a TCP connection to the NGINX stream listener port and transmit the crafted ClientHello before the TLS handshake completes, exploiting the preread phase where NGINX inspects the message without full validation.
  4. Trigger misrouting: The forged preread variables cause NGINX to select an unintended virtual server or backend, routing the attacker's connection to a privileged or internal backend that should be inaccessible.
  5. Access restricted backend: Interact with the misrouted backend to enumerate services, extract sensitive data, or perform further lateral movement within the internal network (GitHub Advisory, Red Hat CVE).

Indicators of compromise

  • Network: Unexpected TLS connections from external IPs reaching internal or privileged backend servers that should not be directly accessible; anomalous stream traffic patterns on NGINX listener ports with malformed or oversized ClientHello messages.
  • Logs: NGINX stream access logs showing connections routed to unexpected upstream groups or backend addresses; TLS handshake errors or SSL_do_handshake() failures in error logs, particularly involving non-TLS 1.3 backends receiving unexpected connections.
  • Process/Behavior: Unusual upstream connection attempts logged by internal backend services originating from the NGINX proxy IP, especially to services not normally proxied through the stream module.

Mitigation and workarounds

F5 has released patched versions addressing this vulnerability. For NGINX Open Source, upgrade to version 1.30.7 (1.30.x branch) or 1.31.9 (1.31.x branch). For NGINX Plus, upgrade to 37.0.7.1 (37.0.x branch) or 37.2.0.1 (37.1.x branch). If immediate patching is not feasible, consider disabling the ngx_stream_ssl_preread_module or restricting access to affected NGINX stream listeners via network-level controls until patches can be applied. Versions that have reached End of Technical Support (EoTS) are not evaluated and should be migrated to supported releases (F5 Advisory, GitHub Advisory).

Community reactions

The vulnerability was noted on social media shortly after disclosure, with at least one post on X (formerly Twitter) referencing the advisory (X/ArtemR). Ireland's NCSC published a brief advisory PDF covering F5 NGINX vulnerabilities disclosed in the same batch (NCSC Ireland). Coverage also appeared on Linux-focused community sites noting the emergency update patching multiple CVEs in NGINX 1.31.9 and 1.30.7 (Linux Compatible). The NGINX security advisories page was updated to reflect the new releases (NGINX).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

nginx: 1.22.1-9+deb12u11

Fixed

sid

nginx: 1.30.6-4

Fixed

trixie

nginx: 1.26.3-3+deb13u11

Fixed

Ubuntu

Fixed

bionic (esm-infra)

nginx: 1.14.0-0ubuntu1.11+esm7

Fixed

devel

nginx: 1.30.6-3ubuntu2

Affected

focal (esm-infra)

nginx: 1.18.0-0ubuntu1.7+esm6

Fixed

jammy

nginx: 1.18.0-6ubuntu14.24

Fixed

noble

nginx: 1.24.0-2ubuntu7.21

Fixed

resolute

nginx: 1.28.3-2ubuntu1.13

Fixed

trusty (esm-infra-legacy)

nginx

Not Affected

xenial (esm-infra-legacy)

nginx

Not Affected

RHEL / CentOS

Affected

RHEL 8

nginx:1.24/nginx.src

Affected

RHEL 9

nginx.src

Affected

RHEL 10

nginx.src

Affected

Alpine

Fixed

edge

nginx: 1.30.7-r0

Fixed

v3.21

nginx: 1.26.3-r4

Fixed

v3.22

nginx: 1.28.3-r8

Fixed

v3.23

nginx: 1.28.3-r8

Fixed

Source: This report was generated using AI

Related NGINX vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-123634CRITICAL9.2
  • NGINX logoNGINX
  • nginx:1.26::nginx
NoYesNov 18, 2026
CVE-2026-123633CRITICAL9.2
  • NGINX logoNGINX
  • nginx-mod-stream-geoip-debuginfo
NoYesNov 18, 2026
CVE-2026-123007CRITICAL9.2
  • NGINX logoNGINX
  • openresty
NoYesNov 18, 2026
CVE-2026-125283MEDIUM6.9
  • NGINX logoNGINX
  • nginx:1.24::nginx-filesystem
NoYesNov 18, 2026
CVE-2026-123640MEDIUM6.9
  • NGINX logoNGINX
  • nginx:1.24::nginx-mod-stream
NoYesNov 18, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management