Skip to content
VulniPulse
Medium 2 vendors · 2 advisories

CVE-2026-120993: NGINX ngx_stream_ssl_module vulnerability

CVE-2026-120993 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
6.9 (F5), 5.3 (Red Hat)
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · base score 6.9, scored by f5Attack vector: network. Attack complexity: low. Attack requirements: none. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: none. Integrity impact on the vulnerable system: none. Availability impact on the vulnerable system: low. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-476 NULL Pointer Dereference
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
Fixed releases
  • F5: 37.3.0.1, 1.31.9
  • Red Hat: nginx-main-1.30.6-1.hum1, RHSA-2026:83427
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-120993; 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 use the ngx_stream_ssl_module module with dynamic certificate loading and the ngx_stream_proxy_module module with the proxy_protocol v2 directive, an abbreviated SSL handshake can cause a worker process to terminate. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system. This is a data plane vulnerability only; there is no control plane exposure. 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-120993?

Upgrade to a fixed release named by the vendor:

  • F5: 37.3.0.1, 1.31.9
  • Red Hat: nginx-main-1.30.6-1.hum1, RHSA-2026:83427
  • To mitigate this vulnerability, apply one of the following configuration changes to affected stream configurations: 1. Replace dynamic certificate loading: Avoid using variables in the `ssl_certificate` and `ssl_certificate_key` directives within the stream context. Define explicit static file paths for certificates and private keys within individual `server` blocks. 2. Remove PROXY protocol version 2: If backend metadata forwarding is not strictly necessary, remove or disable the `proxy_protocol` directive within the affected stream `proxy_pass` blocks. After editing `/etc/nginx/nginx.conf` or the relevant configuration file in `/etc/nginx/conf.d/`, validate the configuration and reload the service: ``` nginx -t systemctl reload nginx ``` 3. Restrict network access: Limit incoming traffic to the stream proxy port to trusted client IP addresses using firewalld: ``` firewall-cmd --permanent --zone=trusted --add-source= firewall-cmd --reload ``` Warning: Reloading the NGINX service or firewalld applies configuration changes immediately. Always run `nginx -t` to verify syntax before reloading to prevent configuration errors from interrupting service availability. Caveats: Using static certificate directives requires separate server blocks for each domain, which increases administrative overhead. Disabling PROXY protocol disables client IP and port propagation to backend stream targets. Restricting network access blocks untrusted or public clients from reaching the stream service. (Red Hat)
  • Workaround: Use one of the following options: * Disable proxy_protocol v2; by setting proxy_protocol off; or using v1 with proxy_protocol on; * Disable abbreviated SSL handshakes by setting both ssl_session_tickets off; and ssl_session_cache off;. Note: nginx built with BoringSSL or AWS-LC is not affected (CVE.org record)

Vendor advisories for CVE-2026-120993

F5

1 advisory

Red Hat

1 advisory
  • Advisory severityMedium5.3

    Medium [CVE-2026-120993] CVE-2026-120993

    CVE-2026-120993Source published Source updated

    CVE-2026-120993. Red Hat rates this moderate (CVSS 5.3). Weakness: CWE-476. Red Hat lists fixing advisory RHSA-2026:83427 with package nginx-main-1.30.6-1.hum1. 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
    • nginx-main-1.30.6-1.hum1
    • RHSA-2026:83427
    Mitigation guidance
    • To mitigate this vulnerability, apply one of the following configuration changes to affected stream configurations: 1. Replace dynamic certificate loading: Avoid using variables in the `ssl_certificate` and `ssl_certificate_key` directives within the stream context. Define explicit static file paths for certificates and private keys within individual `server` blocks. 2. Remove PROXY protocol version 2: If backend metadata forwarding is not strictly necessary, remove or disable the `proxy_protocol` directive within the affected stream `proxy_pass` blocks. After editing `/etc/nginx/nginx.conf` or the relevant configuration file in `/etc/nginx/conf.d/`, validate the configuration and reload the service: ``` nginx -t systemctl reload nginx ``` 3. Restrict network access: Limit incoming traffic to the stream proxy port to trusted client IP addresses using firewalld: ``` firewall-cmd --permanent --zone=trusted --add-source=<trusted_ip_or_range> firewall-cmd --reload ``` Warning: Reloading the NGINX service or firewalld applies configuration changes immediately. Always run `nginx -t` to verify syntax before reloading to prevent configuration errors from interrupting service availability. Caveats: Using static certificate directives requires separate server blocks for each domain, which increases administrative overhead. Disabling PROXY protocol disables client IP and port propagation to backend stream targets. Restricting network access blocks untrusted or public clients from reaching the stream service.

References

Timeline

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

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