# CVE-2026-123640: NGINX ngx_stream_ssl_preread_module stream routing bypass

Source: https://junglewise.ai/threats/cve-2026-123640-description-when-nginx-plus-or-nginx-open-source-is-configured  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-18. Updated: 2026-11-18  
License: CC BY 4.0 with a link back

CVE-2026-123640 · Severity: medium · CVSS 5.3 · Published 2026-11-18

NGINX Plus and NGINX Open Source can be configured with a module that inspects SSL/TLS connection metadata to route traffic to the correct backend server. A specially crafted SSL/TLS handshake message from an unauthenticated attacker can forge the routing metadata, allowing the connection to be redirected to unintended backend servers. An attacker could exploit this to access sensitive internal systems that should be unreachable.

Technologies: [NGINX Open Source](https://junglewise.ai/threats/technologies/open-source), [NGINX Plus](https://junglewise.ai/threats/technologies/plus). Vendors: [NGINX](https://junglewise.ai/threats/vendors/nginx).

## Quick answers

**Is CVE-2026-123640 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-123640 being exploited in the wild.

**How severe is CVE-2026-123640?** Medium severity, with a CVSS score of 5.3, published 18 November 2026.

**Which products and versions are affected?** NGINX NGINX Plus; NGINX NGINX Open Source.

**Is there a fix for CVE-2026-123640?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-123640 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-123640?** Check whether you run NGINX Open Source or NGINX Plus. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The ngx_stream_ssl_preread_module uses ClientHello message fields to determine stream routing decisions. A malformed ClientHello can cause the module to set incorrect variable values, bypassing stream segmentation and routing logic. The attack requires network access to NGINX and no authentication; the module's variables are forged before backend selection occurs, affecting only the data plane.

## Affected products

- NGINX NGINX Plus
- NGINX NGINX Open Source

## Timeline

- 2026-11-18: disclosed

## References

- [https://my.f5.com/manage/s/article/K000163935](https://my.f5.com/manage/s/article/K000163935)

## Related threats

- [NGINX Plus and Open Source segmentation fault in try_files with alias](https://junglewise.ai/threats/cve-2026-125283-when-nginx-plus-or-nginx-open-source-is-configured-to-use-the)
- [NGINX Plus and Open Source use-after-free in proxy with SSI](https://junglewise.ai/threats/cve-2026-123634-this-issue-occurs-when-nginx-plus-or-nginx-open-source-is)
- [NGINX Plus and NGINX Open Source use-after-free in HTTP/2](https://junglewise.ai/threats/cve-2026-123633-when-nginx-plus-or-nginx-open-source-is-configured-to-use-http-2)
- [NGINX heap buffer overflow in HTTP/2 flow control](https://junglewise.ai/threats/cve-2026-123007-this-issue-affects-nginx-plus-or-nginx-open-source)
- [NGINX Plus and Open Source worker process termination with SSL and proxy protocol](https://junglewise.ai/threats/cve-2026-120993-when-nginx-plus-or-nginx-open-source-is-configured-to-use-the)
