Skip to content
Threat Brief

← All advisories

CVE-2026-120967

Medium 6.3No known exploitationFix available

NGINX ngx_stream_ssl_module vulnerability

Record last updated

CVSS score

6.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

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

CISA remediation deadline

None

Not in the KEV catalog

Description

When NGINX Plus or NGINX Open Source is configured to require client certificates ("ssl_verify_client on") in a non-default stream virtual server, a remote attacker could bypass verification of client certificates. Impact: An attacker could leverage this vulnerability to bypass verification of client certificates. 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
To mitigate this vulnerability, configure ssl_verify_client on; in the default server of the shared listening socket, or move the stream virtual server requiring client certificates to its own dedicated listening address and port. Note: Configurations where the default server has the ssl_verify_client on; are not affected. 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.25.5 before 1.30.71.30.7CVE Program
F5NGINX Open Sourcefrom 1.31.0 before 1.31.91.31.9CVE Program
F5NGINX Plusfrom 37.0.0 before 37.0.8.137.0.8.1CVE Program
F5NGINX Plusfrom 37.1.0 before 37.3.0.137.3.0.1CVE Program
F5NGINX PlusR33Not documentedCVE Program
Microsoftazl3 nginx 0.0.0-1 on Azure Linux 3.0Not documented1.30.6-2Microsoft MSRC

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