CVE-2026-118899: NGINX TLSv1.3 vulnerability
CVE-2026-118899 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- High
- CVSS base score
- 8.7 (F5), 7.5 (Red Hat)
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N· base score 8.7, 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: high. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.- Weakness
- CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
- Fixed releases
- F5: 1.31.9, 1.30.7, 37.2.1.1, 37.0.8.1
- 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-118899; each belongs to its advisory, not to every product listed. How records are collected and checked.
Description
When using the listen directive with the ssl parameter in the http block with TLSv1.3 enabled, an attacker can use a specially crafted TLS connection to cause an infinite loop in the NGINX worker process while reading the HTTP request body. As a result, the worker process stops accepting new connections and processing existing connections. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. Impact: This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) of NGINX. 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-118899?
Upgrade to a fixed release named by the vendor:
- F5: 1.31.9, 1.30.7, 37.2.1.1, 37.0.8.1
- Disable TLSv1.3 protocol support in the NGINX configuration to restrict connections to TLSv1.2, or restrict access to trusted networks using firewall rules. To disable TLSv1.3: 1. Edit the NGINX configuration file (such as `/etc/nginx/nginx.conf` or configuration snippets under `/etc/nginx/conf.d/`). 2. Locate the `ssl_protocols` directive within the `http` or `server` blocks and set it to allow only TLSv1.2: ``` ssl_protocols TLSv1.2; ``` 3. Verify the configuration syntax: ```sh nginx -t ``` 4. Reload the NGINX service to apply configuration changes: ```sh systemctl reload nginx ``` Alternatively, if the service only needs to be reached by specific clients, use firewalld to limit network exposure: ```sh firewall-cmd --permanent --zone=trusted --add-source= firewall-cmd --reload ``` Caveats: Disabling TLSv1.3 prevents clients that strictly require TLSv1.3 from connecting and removes the performance and cryptographic improvements introduced in that version. Warning: Reloading the NGINX service is required for configuration changes to take effect and may cause momentary disruption to existing connections. (Red Hat)
- Workaround: None. (CVE.org record)
Vendor advisories for CVE-2026-118899
F5
1 advisory- Advisory severityHigh8.7
High [CVE-2026-118899] When using the listen directive with the ssl parameter in the http block with TLSv1.3 enabled, an attacker can use a specially crafted TLS connection to cause an infinite loop in the NGINX worker process while reading the HTTP request body
CVE-2026-118899Source published Source updated
When using the listen directive with the ssl parameter in the http block with TLSv1.3 enabled, an attacker can use a specially crafted TLS connection to cause an infinite loop in the NGINX worker process while reading the HTTP request body. As a result, the worker process stops accepting new connections and processing existing connections. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. Impact: This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) of NGINX. There is no control plane exposure; this is a data plane issue only. Affected products named by the advisory: NGINX Open Source; NGINX Plus.
- Affected products in this advisory
- NGINX Open Source
- NGINX Plus
- Source-reported affected versions
- NGINX Open Source 1.31.0 before 1.31.9
- NGINX Open Source 1.30.0 before 1.30.7
- NGINX Open Source 1.31.0
- NGINX Plus 37.2.0.1 before 37.2.1.1
2 more entries in the full advisory.
- Source-reported fixed versions
- 1.31.9
- 1.30.7
- 37.2.1.1
- 37.0.8.1
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
- Workarounds
- When using the listen directive with the ssl parameter in the http block with TLSv1.3 enabled, an attacker can use a specially crafted TLS connection to cause an infinite loop in the NGINX worker process while reading the HTTP request body.
Red Hat
1 advisory- Advisory severityHigh7.5
High [CVE-2026-118899] Denial of Service via crafted TLS connection
CVE-2026-118899Source published Source updated
Denial of Service via crafted TLS connection. Red Hat rates this important (CVSS 7.5). Weakness: CWE-835. 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
- Disable TLSv1.3 protocol support in the NGINX configuration to restrict connections to TLSv1.2, or restrict access to trusted networks using firewall rules. To disable TLSv1.3: 1. Edit the NGINX configuration file (such as `/etc/nginx/nginx.conf` or configuration snippets under `/etc/nginx/conf.d/`). 2. Locate the `ssl_protocols` directive within the `http` or `server` blocks and set it to allow only TLSv1.2: ``` ssl_protocols TLSv1.2; ``` 3. Verify the configuration syntax: ```sh nginx -t ``` 4. Reload the NGINX service to apply configuration changes: ```sh systemctl reload nginx ``` Alternatively, if the service only needs to be reached by specific clients, use firewalld to limit network exposure: ```sh firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_RANGE> firewall-cmd --reload ``` Caveats: Disabling TLSv1.3 prevents clients that strictly require TLSv1.3 from connecting and removes the performance and cryptographic improvements introduced in that version. Warning: Reloading the NGINX service is required for configuration changes to take effect and may cause momentary disruption to existing connections.
References
- CVE-2026-118899 recordCVE.org
- CVE-2026-118899 detailNVD
- my.f5.com/manage/s/article/K000163930vendor-advisory, patch
Timeline
- CVE record published
- First vendor advisory listed by VulniPulse
More F5 advisories
CVE-2026-125283Nov 18, 2026When NGINX Plus or NGINX Open Source is configured to use the try_files and aliasCVE-2026-120967Nov 18, 2026When NGINX Plus or NGINX Open Source is configured to require client certificatesCVE-2026-120993Nov 18, 2026When NGINX Plus or NGINX Open Source is configured to use the ngx_stream_ssl_module moduleCVE-2026-121810Nov 18, 2026This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3CVE-2026-123007Nov 18, 2026This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2CVE-2026-113425Nov 18, 2026When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic
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.