Skip to content
VulniPulse
Medium 2 vendors · 2 advisories

CVE-2026-120967: NGINX ngx_stream_ssl_module vulnerability

CVE-2026-120967 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
6.3 (F5), 4.8 (Red Hat)
CVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · base score 6.3, scored by f5Attack vector: network. Attack complexity: high. Attack requirements: none. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: low. Integrity impact on the vulnerable system: low. Availability impact on the vulnerable system: none. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-1289 Improper Validation of Unsafe Equivalence in Input
Fixed releases
  • F5: 37.3.0.1, 37.0.8.1, 1.31.9, 1.30.7
Vendor advisories
2 from F5, Red Hat
Assigned by
f5 (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-120967; each belongs to its advisory, not to every product listed. How records are collected and checked.

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.

Text from the CVE.org record (f5).

How do I fix CVE-2026-120967?

Upgrade to a fixed release named by the vendor:

  • F5: 37.3.0.1, 37.0.8.1, 1.31.9, 1.30.7
  • Restrict network access to the port hosting the affected stream service using firewalld so that only trusted client IP addresses or subnets can establish connections. 1. Add the authorized client IP address or network range to the trusted firewall zone: # firewall-cmd --permanent --zone=trusted --add-source=192.0.2.0/24 2. Remove public exposure of the stream service port: # firewall-cmd --permanent --zone=public --remove-port=8443/tcp 3. Apply the firewall configuration: # firewall-cmd --reload Caveats: Restricting network access by source IP address requires maintaining an accurate allowlist of authorized client networks and is unsuitable for public-facing deployments with dynamic client IP addresses. Warning: Reloading the firewall configuration can temporarily disrupt active network connections. (Red Hat)
  • Workaround: 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. (CVE.org record)

Vendor advisories for CVE-2026-120967

F5

1 advisory

Red Hat

1 advisory
  • Advisory severityMedium4.8

    Medium [CVE-2026-120967] CVE-2026-120967

    CVE-2026-120967Source published Source updated

    CVE-2026-120967. Red Hat rates this moderate (CVSS 4.8). Weakness: CWE-295. Affected product named by the advisory: Red Hat Hardened Images.

    Related products — impact not confirmed
    • Red Hat Hardened Images
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    • Restrict network access to the port hosting the affected stream service using firewalld so that only trusted client IP addresses or subnets can establish connections. 1. Add the authorized client IP address or network range to the trusted firewall zone: # firewall-cmd --permanent --zone=trusted --add-source=192.0.2.0/24 2. Remove public exposure of the stream service port: # firewall-cmd --permanent --zone=public --remove-port=8443/tcp 3. Apply the firewall configuration: # firewall-cmd --reload Caveats: Restricting network access by source IP address requires maintaining an accurate allowlist of authorized client networks and is unsuitable for public-facing deployments with dynamic client IP addresses. Warning: Reloading the firewall configuration can temporarily disrupt active network connections.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse

All F5 advisories

Get an email when F5 publishes the next one.

See F5's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about F5