Skip to main content
Menu
CVEs

CVE

F5 NGINX Plus client certificate bypass in ngx_stream_ssl_module

CVE-2026-120967EUVD-2026-128957Published Updated Summary written by a modelNeeds attention

4.8MediumCNA
Exploited
Public exploit code, no confirmed attacks
Fix
Fixed in NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7
Who is exposed
Not reported

Do first: Upgrade to a fixed version: NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7.

Summary

F5 NGINX Plus and F5 NGINX Open Source are affected when they are configured to require client certificates in a non-default stream virtual server. A remote attacker who does not need to log in could bypass client certificate verification.

Original 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.

cve.now Index

61Pcve.now Index 61 of 100 · methodology v3 · provisional
  • Exploitation22/40Public exploit on Exploit-DB or GitHub
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach17/20Affects nginx (a widely deployed server, runtime, framework or database)
  • Severity4.8/10CVSS 4.8
  • No patch0/5No signal

What would change the score

  • Would score about 84 if added to CISA KEV
  • Would score about 79 if CISA's SSVC rates exploitation active
  • Would score about 66 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-120967 (NGINX ngx_stream_ssl_module vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120967 (entry last updated 2026-11-18):
Affected:
- F5 NGINX Plus: from 37.1.0, fixed in 37.3.0.1; from 37.0.0, fixed in 37.0.8.1; from R33
- F5 NGINX Open Source: from 1.31.0, fixed in 1.31.9; from 1.25.5, fixed in 1.30.7
Fixed versions: 37.3.0.1, 37.0.8.1, 1.31.9, 1.30.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120967 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120967 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://my.f5.com/manage/s/article/K000163934
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120967
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120967"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated
  5. Exploit code on GitHub

    LLCForge/CVE-2026-120967

Affected versions

  • F5 NGINX Plus

    From 37.1.0 · fixed in 37.3.0.1; From 37.0.0 · fixed in 37.0.8.1; From R33

  • F5 NGINX Open Source

    From 1.31.0 · fixed in 1.31.9; From 1.25.5 · fixed in 1.30.7

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-120967
RecordNVD · CVE-2026-120967
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · LLCForge/CVE-2026-120967 · Repository
Other links 1
Patchmy.f5.com · manage/s/article/K000163934

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-120967

Is CVE-2026-120967 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data

Which versions are affected by CVE-2026-120967?

NGINX Plus: from 37.1.0 before 37.3.0.1; from 37.0.0 before 37.0.8.1; from R33. NGINX Open Source: from 1.31.0 before 1.31.9; from 1.25.5 before 1.30.7.Source: cve.now feed data

How do I fix CVE-2026-120967?

Upgrade to a fixed version: NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7.Source: cve.now feed data

More CVEs