CVE-2026-118899

Description

A flaw was found in NGINX. A remote, unauthenticated attacker could cause a Denial of Service (DoS) by establishing a specially crafted Transport Layer Security (TLS) connection. Under configurations with TLS version 1.3 enabled, this triggers an infinite loop in the worker process while reading an HTTP request body, causing the process to hang and stop handling connections.

Statement

This vulnerability is rated as an Important severity flaw because an unauthenticated remote attacker can cause a complete denial of service against NGINX services without requiring special access or privileges. In standard Red Hat Enterprise Linux environments where NGINX terminates TLS connections with TLSv1.3 active, processing malformed request payloads forces worker processes into an infinite loop. Sustained attempts can hang all available worker processes, denying service to legitimate clients while leaving system data confidentiality and integrity intact.

Mitigation

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.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/A7.5
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Amplification

An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.

Frequently Asked Questions

Want to get errata notifications? Sign up here.