cve.bz

CVE-2026-118899 NGINX TLSv1.3 vulnerability

8.7 highEPSS 3.8%

High (8.7) in f5. EPSS 3.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

8.7 high
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

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
3.8% estimated probability of exploitation activity in the next 30 days; 90th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
Assigned by
f5 (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-118899 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118899?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118899?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118899 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
F5 NGINX Open Sourcefrom 1.31.0 before 1.31.9
F5 NGINX Open Sourcefrom 1.30.0 before 1.30.7
F5 NGINX Open Source1.31.0 and later
F5 NGINX Plusfrom 37.2.0.1 before 37.2.1.1
F5 NGINX Plusfrom 37.0.0 before 37.0.8.1
F5 NGINX PlusR33 and later

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12nginx1.22.1-9+deb12u11DEBIAN-CVE-2026-118899 DLA-4918-1
Debian13nginx1.26.3-3+deb13u11DEBIAN-CVE-2026-118899 DSA-6642-1
Debian14nginx1.30.6-4DEBIAN-CVE-2026-118899
Ubuntu22.04:LTS, Pro:18.04:LTS, Pro:20.04:LTSnginxno fix listedUBUNTU-CVE-2026-118899
Ubuntu24.04:LTSnginx1.24.0-2ubuntu7.20UBUNTU-CVE-2026-118899
Ubuntu26.04:LTSnginx1.28.3-2ubuntu1.13UBUNTU-CVE-2026-118899
Ubuntu26.10nginx1.30.4-7ubuntu1.2UBUNTU-CVE-2026-118899
openSUSETumbleweednginx1.31.9-1.1openSUSE-SU-2026:12599-1
AlmaLinux8nginx, nginx-mod-mail, nginx-mod-devel and 6 more1:1.24.0-3.module_el8.10.0+4384+8a1ec6ac.9.alma.2ALSA-2026:100747
AlmaLinux9nginx, nginx-core, nginx-mod-mail and 7 more2:1.20.1-32.el9_9.2.alma.2ALSA-2026:100748
AlmaLinux9nginx, nginx-core, nginx-mod-mail and 7 more2:1.26.3-10.module_el9.9.0+364+649eade1.4ALSA-2026:100745
AlmaLinux9nginx-core, nginx-mod-mail, nginx-mod-devel and 4 more1:1.24.0-9.module_el9.9.0+365+792376e1.4.alma.2ALSA-2026:100746
AlmaLinux10nginx, nginx-core, nginx-mod-mail and 7 more2:1.26.3-16.el10_3.3.alma.1ALSA-2026:100744
Rocky Linux8nginx, nginx-mod-mail, nginx-debuginfo and 13 more1:1.24.0-3.module+el8.10.0+40469+da1f451a.9RLSA-2026:100747
Rocky Linux9nginx, nginx-core, nginx-mod-mail and 15 more2:1.20.1-32.el9_9.2.rocky.0.1RLSA-2026:100748
Rocky Linux9nginx, nginx-core, nginx-mod-mail and 15 more2:1.26.3-10.module+el9.9.0+40471+ba1db702.4RLSA-2026:100745
Rocky Linux10nginx, nginx-core, nginx-mod-mail and 15 more2:1.26.3-16.el10_3.3RLSA-2026:100744
Alpinev3.21nginx1.26.3-r4ALPINE-CVE-2026-118899
Alpinev3.22, v3.23nginx1.28.3-r8ALPINE-CVE-2026-118899
Alpinev3.24nginx1.30.7-r0ALPINE-CVE-2026-118899
Azure Linux3nginx1.30.6-2AZL-114601
Alpaquita23, 25, streamnginx, nginx-base1.30.7-r0BELL-CVE-2026-118899
BellSoft Hardened Containers23, 25, streamnginx-base1.30.7-r0BELL-CVE-2026-118899

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Important.

Red Hat's 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.

Red Hat's 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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10nginx-2:1.26.3-16.el10_3.3Fixed 2026-11-20RHSA-2026:100744
Red Hat Enterprise Linux 8nginx:1.24-8100020261119142731.489197e6Fixed 2026-11-20RHSA-2026:100747
Red Hat Enterprise Linux 9nginx:1.26-9090020261119140335.9Fixed 2026-11-20RHSA-2026:100745
Red Hat Enterprise Linux 9nginx:1.24-9090020261119141016.9Fixed 2026-11-20RHSA-2026:100746
Red Hat Enterprise Linux 9nginx-2:1.20.1-32.el9_9.2Fixed 2026-11-20RHSA-2026:100748
Red Hat Enterprise Linux 9.8 Extended Update Supportnginx:1.24-9080020261119183858.9Fixed 2026-11-20RHSA-2026:100750
Red Hat Enterprise Linux 9.8 Extended Update Supportnginx:1.26-9080020261119210404.9Fixed 2026-11-20RHSA-2026:100751
Red Hat Hardened ImagesnginxAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-118899.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • LLCForge/CVE-2026-118899 Harbor Check: matches CVE 0 stars, Python, created
    CVE-2026-118899 — nginx worker infinite loop (CWE-835) in TLS 1.3 request-body path. CPU exhaustion DoS on nginx 1.13.0–1.31.8. Docker PoC.

History

  1. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON