CVE-2026-123640 (GCVE-0-2026-123640)

Vulnerability from cvelistv5 – Published: 2026-11-18 15:23 – Updated: 2026-11-18 16:51
VLAI
Title
NGINX ngx_stream_ssl_preread_module vulnerability
Summary
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.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 16:35 UTC
CWE
  • CWE-1289 - Improper Validation of Unsafe Equivalence in Input
Assigner
f5 CNA under the mitre root
CNA scorecard B 86/100 over 56 records in the last 180 days details
References
URL Tags
https://my.f5.com/manage/s/article/K000163935 vendor-advisorypatch
Impacted products
Vendor Product Version CPE status
F5 NGINX Plus Affected: 37.1.0 , < 37.2.0.1 (custom)
Affected: 37.0.0 , < 37.0.7.1 (custom)
Affected: R33 , < * (custom)
guessed Create a notification for this product.
F5 NGINX Open Source Affected: 1.31.0 , < 1.31.9 (semver)
Affected: 1.30.0 , < 1.30.7 (semver)
Affected: 1.15.2 , < * (semver)
guessed Create a notification for this product.
Date Public
2026-11-18 15:00
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-123640",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-18T16:35:38.347306Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-18T16:51:01.723Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unknown",
          "modules": [
            "ngx_stream_ssl_preread_module"
          ],
          "product": "NGINX Plus",
          "vendor": "F5",
          "versions": [
            {
              "lessThan": "37.2.0.1",
              "status": "affected",
              "version": "37.1.0",
              "versionType": "custom"
            },
            {
              "lessThan": "37.0.7.1",
              "status": "affected",
              "version": "37.0.0",
              "versionType": "custom"
            },
            {
              "lessThan": "*",
              "status": "affected",
              "version": "R33",
              "versionType": "custom"
            }
          ]
        },
        {
          "defaultStatus": "unknown",
          "modules": [
            "ngx_stream_ssl_preread_module"
          ],
          "product": "NGINX Open Source",
          "vendor": "F5",
          "versions": [
            {
              "lessThan": "1.31.9",
              "status": "affected",
              "version": "1.31.0",
              "versionType": "semver"
            },
            {
              "lessThan": "1.30.7",
              "status": "affected",
              "version": "1.30.0",
              "versionType": "semver"
            },
            {
              "lessThan": "*",
              "status": "affected",
              "version": "1.15.2",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "F5 acknowledges Vivek Parikh of BreachX Zero Day Labs using Typhon AI Mil v2 for bringing this issue to our attention and following the highest standards of coordinated disclosure."
        }
      ],
      "datePublic": "2026-11-18T15:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003eDescription\u003cbr\u003e\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003e\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003eWhen NGINX Plus or NGINX Open Source is configured with the \u003cb\u003engx_stream_ssl_preread_module\u003c/b\u003e module, a specially crafted ClientHello message from an unauthenticated attacker causes forged values of the \u003cb\u003engx_stream_ssl_preread_module\u003c/b\u003e 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.\u003c/span\u003e\u003cbr\u003e\u003c/span\u003e\u003c/span\u003e\u003cbr\u003eImpact\u003cbr\u003e\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003eThis vulnerability may allow an attacker to forge values of the \u003cb\u003engx_stream_ssl_preread_module\u003c/b\u003e 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.\u003c/span\u003e\n\n\u003cbr\u003e\u003cbr\u003e\n\n\nNote: Software versions which have reached End of Technical Support (EoTS) are not evaluated."
            }
          ],
          "value": "Description\nWhen 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.\n\nImpact\nThis 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.\n\n\n\n\n\n\nNote: Software versions which have reached End of Technical Support (EoTS) are not evaluated."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 6.9,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-1289",
              "description": "CWE-1289 Improper Validation of Unsafe Equivalence in Input",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-18T15:23:27.556Z",
        "orgId": "9dacffd4-cb11-413f-8451-fbbfd4ddc0ab",
        "shortName": "f5"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory",
            "patch"
          ],
          "url": "https://my.f5.com/manage/s/article/K000163935"
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "NGINX ngx_stream_ssl_preread_module vulnerability",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003e\u003c/p\u003e\u003cp\u003eDisable the \u003cstrong\u003essl_preread\u003c/strong\u003e directive in favor of SSL/TLS termination on NGINX. For more information, refer to \u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html\"\u003ehttps://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html\u003c/a\u003e\u003c/p\u003e\u003cp\u003eFor example, the following configuration includes the \u003cstrong\u003essl_preread on;\u003c/strong\u003e directive:\u003c/p\u003e\u003cp\u003e\u003c/p\u003e\u003cp\u003estream {\u003cbr\u003e\u0026nbsp; \u0026nbsp; log_format sni \"PREREAD_SNI=[$ssl_preread_server_name] -\u0026gt; [$backend]\";\u003cbr\u003e\u0026nbsp; \u0026nbsp; access_log /var/log/nginx/stream.log sni;\u003cbr\u003e\u0026nbsp; \u0026nbsp; map $ssl_preread_server_name $backend {\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; internal.test \u0026nbsp; 127.0.0.1:9002; \u0026nbsp; # privileged backend\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; default  \u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp;127.0.0.1:9001; \u0026nbsp; # public backend\u003cbr\u003e\u0026nbsp; \u0026nbsp; }\u003cbr\u003e\u0026nbsp; \u0026nbsp; server {\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; listen 9443;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; ssl_preread on;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; proxy_pass $backend;\u003cbr\u003e\u0026nbsp; \u0026nbsp; }\u003cbr\u003e}\u003c/p\u003e\u003cp\u003eTo mitigate the issue for this configuration, make the following changes:\u003c/p\u003e\u003cul\u003e\u003cli\u003eRemove the \u003cstrong\u003essl_preread\u003c/strong\u003e directive.\u003c/li\u003e\u003cli\u003eTerminate TLS on NGINX by adding the following:\u003cul\u003e\u003cli\u003eChange the listener to ssl.\u003c/li\u003e\u003cli\u003eConfigure a certificate and key.\u003c/li\u003e\u003cli\u003eReplacing \u003cstrong\u003e$ssl_preread_server_name\u003c/strong\u003e with \u003cstrong\u003e$ssl_server_name\u003c/strong\u003e to use SNI-based routing.\u003c/li\u003e\u003c/ul\u003e\u003c/li\u003e\u003c/ul\u003e\u003cp\u003estream {\u003cbr\u003e\u0026nbsp; \u0026nbsp; log_format sni \"TLS_SNI=[$ssl_server_name] -\u0026gt; [$backend]\";\u003cbr\u003e\u0026nbsp; \u0026nbsp; access_log /var/log/nginx/stream.log sni;\u003cbr\u003e\u0026nbsp; \u0026nbsp; map $ssl_server_name $backend {\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; internal.test \u0026nbsp; 127.0.0.1:9002; \u0026nbsp; # privileged backend\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; default  \u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp;127.0.0.1:9001; \u0026nbsp; # public backend\u003cbr\u003e\u0026nbsp; \u0026nbsp; }\u003cbr\u003e\u0026nbsp; \u0026nbsp; server {\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; listen 9443 ssl;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; ssl_certificate \u0026nbsp; \u0026nbsp; /etc/nginx/ssl/fullchain.pem;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; ssl_certificate_key /etc/nginx/ssl/privkey.pem;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; ssl_protocols \u0026nbsp; \u0026nbsp; \u0026nbsp; TLSv1.2 TLSv1.3;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; # ssl_preread removed; NGINX terminates client TLS.\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; proxy_pass $backend;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; # Use these if the backends still expect TLS.\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; proxy_ssl on;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; proxy_ssl_server_name on;\u003cbr\u003e\u0026nbsp; \u0026nbsp; \u0026nbsp; \u0026nbsp; proxy_ssl_name $ssl_server_name;\u003cbr\u003e\u0026nbsp; \u0026nbsp; }\u003cbr\u003e}\u003c/p\u003e\u003cp\u003eAfter making the configuration changes, validate the configuration and reload, using the following commands:\u003c/p\u003e\u003cp\u003enginx -t\u003cbr\u003enginx -s reload\u003c/p\u003e"
            }
          ],
          "value": "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 \n\nFor example, the following configuration includes the ssl_preread on; directive:\n\n\n\nstream {\n\u00a0 \u00a0 log_format sni \"PREREAD_SNI=[$ssl_preread_server_name] -\u003e [$backend]\";\n\u00a0 \u00a0 access_log /var/log/nginx/stream.log sni;\n\u00a0 \u00a0 map $ssl_preread_server_name $backend {\n\u00a0 \u00a0 \u00a0 \u00a0 internal.test \u00a0 127.0.0.1:9002; \u00a0 # privileged backend\n\u00a0 \u00a0 \u00a0 \u00a0 default  \u00a0 \u00a0 \u00a0 \u00a0 \u00a0127.0.0.1:9001; \u00a0 # public backend\n\u00a0 \u00a0 }\n\u00a0 \u00a0 server {\n\u00a0 \u00a0 \u00a0 \u00a0 listen 9443;\n\u00a0 \u00a0 \u00a0 \u00a0 ssl_preread on;\n\u00a0 \u00a0 \u00a0 \u00a0 proxy_pass $backend;\n\u00a0 \u00a0 }\n}\n\nTo mitigate the issue for this configuration, make the following changes:\n\n  *  Remove the ssl_preread directive.\n  *  Terminate TLS on NGINX by adding the following:  *  Change the listener to ssl.\n  *  Configure a certificate and key.\n  *  Replacing $ssl_preread_server_name with $ssl_server_name to use SNI-based routing.\n\n\n\n\n\nstream {\n\u00a0 \u00a0 log_format sni \"TLS_SNI=[$ssl_server_name] -\u003e [$backend]\";\n\u00a0 \u00a0 access_log /var/log/nginx/stream.log sni;\n\u00a0 \u00a0 map $ssl_server_name $backend {\n\u00a0 \u00a0 \u00a0 \u00a0 internal.test \u00a0 127.0.0.1:9002; \u00a0 # privileged backend\n\u00a0 \u00a0 \u00a0 \u00a0 default  \u00a0 \u00a0 \u00a0 \u00a0 \u00a0127.0.0.1:9001; \u00a0 # public backend\n\u00a0 \u00a0 }\n\u00a0 \u00a0 server {\n\u00a0 \u00a0 \u00a0 \u00a0 listen 9443 ssl;\n\u00a0 \u00a0 \u00a0 \u00a0 ssl_certificate \u00a0 \u00a0 /etc/nginx/ssl/fullchain.pem;\n\u00a0 \u00a0 \u00a0 \u00a0 ssl_certificate_key /etc/nginx/ssl/privkey.pem;\n\u00a0 \u00a0 \u00a0 \u00a0 ssl_protocols \u00a0 \u00a0 \u00a0 TLSv1.2 TLSv1.3;\n\u00a0 \u00a0 \u00a0 \u00a0 # ssl_preread removed; NGINX terminates client TLS.\n\u00a0 \u00a0 \u00a0 \u00a0 proxy_pass $backend;\n\u00a0 \u00a0 \u00a0 \u00a0 # Use these if the backends still expect TLS.\n\u00a0 \u00a0 \u00a0 \u00a0 proxy_ssl on;\n\u00a0 \u00a0 \u00a0 \u00a0 proxy_ssl_server_name on;\n\u00a0 \u00a0 \u00a0 \u00a0 proxy_ssl_name $ssl_server_name;\n\u00a0 \u00a0 }\n}\n\nAfter making the configuration changes, validate the configuration and reload, using the following commands:\n\nnginx -t\nnginx -s reload"
        }
      ],
      "x_generator": {
        "engine": "F5 SIRTBot v1.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "9dacffd4-cb11-413f-8451-fbbfd4ddc0ab",
    "assignerShortName": "f5",
    "cveId": "CVE-2026-123640",
    "datePublished": "2026-11-18T15:23:27.556Z",
    "dateReserved": "2026-11-09T18:42:53.901Z",
    "dateUpdated": "2026-11-18T16:51:01.723Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unknown",
                "modules": [
                  "ngx_stream_ssl_preread_module"
                ],
                "product": "NGINX Plus",
                "vendor": "F5",
                "versions": [
                  {
                    "lessThan": "37.2.0.1",
                    "status": "affected",
                    "version": "37.1.0",
                    "versionType": "custom"
                  },
                  {
                    "lessThan": "37.0.7.1",
                    "status": "affected",
                    "version": "37.0.0",
                    "versionType": "custom"
                  },
                  {
                    "lessThan": "*",
                    "status": "affected",
                    "version": "R33",
                    "versionType": "custom"
                  }
                ]
              },
              {
                "defaultStatus": "unknown",
                "modules": [
                  "ngx_stream_ssl_preread_module"
                ],
                "product": "NGINX Open Source",
                "vendor": "F5",
                "versions": [
                  {
                    "lessThan": "1.31.9",
                    "status": "affected",
                    "version": "1.31.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "1.30.7",
                    "status": "affected",
                    "version": "1.30.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "*",
                    "status": "affected",
                    "version": "1.15.2",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "f5sirt@f5.com"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "Description\nWhen 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.\n\nImpact\nThis 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.\n\n\n\n\n\n\nNote: Software versions which have reached End of Technical Support (EoTS) are not evaluated."
          }
        ],
        "id": "CVE-2026-123640",
        "lastModified": "2026-11-18T17:17:33.280",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "LOW",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
                "version": "3.1"
              },
              "exploitabilityScore": 3.9,
              "impactScore": 1.4,
              "source": "f5sirt@f5.com",
              "type": "Secondary"
            }
          ],
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 6.9,
                "baseSeverity": "MEDIUM",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "NONE",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "NONE",
                "vulnIntegrityImpact": "LOW",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "f5sirt@f5.com",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-123640",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-18T16:35:38.347306Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-11-18T16:18:04.677",
        "references": [
          {
            "source": "f5sirt@f5.com",
            "url": "https://my.f5.com/manage/s/article/K000163935"
          }
        ],
        "sourceIdentifier": "f5sirt@f5.com",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-1289"
              }
            ],
            "source": "f5sirt@f5.com",
            "type": "Secondary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-18T17:02:44+00:00",
      "cve": "CVE-2026-123640",
      "id": "CVE-2026-123640",
      "initial_release_date": "2026-11-18T15:23:27.556000+00:00",
      "product_status:known_affected": "1",
      "product_status:known_not_affected": "1",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "nginx: nginx: Stream routing segmentation bypass via crafted TLS ClientHello",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-123640.json",
      "version": "3"
    }
  }
}


Workarounds

CNA · f5
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

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.