Skip to main content
Menu
CVEs

CVE

F5 NGINX Open Source denial of service in TLS request handling

CVE-2026-118899EUVD-2026-128946Published Updated Summary written by a modelNeeds attention

7.5HighCNA
Exploited
Public exploit code, no confirmed attacks
Fix
Fixed in NGINX Open Source 1.31.9, 1.30.7 · NGINX Plus 37.2.1.1, 37.0.8.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: NGINX Open Source 1.31.9, 1.30.7 · NGINX Plus 37.2.1.1, 37.0.8.1.

Summary

A remote, unauthenticated attacker can reach a flaw in F5's NGINX Open Source and NGINX Plus by sending a specially crafted TLS connection, when TLSv1.3 is enabled with the ssl parameter on the listen directive in the http block. The attack sends the NGINX worker process into an endless loop while it reads the HTTP request body, so NGINX stops accepting and handling connections, causing a denial of service.

Original 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.

cve.now Index

67Pcve.now Index 67 of 100 · methodology v3 · provisional
  • Exploitation22/40Public exploit on Exploit-DB or GitHub
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach17/20Affects nginx (a widely deployed server, runtime, framework or database)
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 90 if added to CISA KEV
  • Would score about 85 if CISA's SSVC rates exploitation active
  • Would score about 72 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: NGINX Open Source 1.31.9, 1.30.7 · NGINX Plus 37.2.1.1, 37.0.8.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-118899 (NGINX TLSv1.3 vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-118899 (entry last updated 2026-11-18):
Affected:
- F5 NGINX Open Source: from 1.31.0, fixed in 1.31.9; from 1.30.0, fixed in 1.30.7; from 1.31.0
- F5 NGINX Plus: from 37.2.0.1, fixed in 37.2.1.1; from 37.0.0, fixed in 37.0.8.1; from R33
Fixed versions: 1.31.9, 1.30.7, 37.2.1.1, 37.0.8.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-118899 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118899 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://my.f5.com/manage/s/article/K000163930
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-118899
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-118899"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  5. Record last updated
  6. Exploit code on GitHub

    LLCForge/CVE-2026-118899

Affected versions

  • F5 NGINX Open Source

    From 1.31.0 · fixed in 1.31.9; From 1.30.0 · fixed in 1.30.7; From 1.31.0

  • F5 NGINX Plus

    From 37.2.0.1 · fixed in 37.2.1.1; From 37.0.0 · fixed in 37.0.8.1; From R33

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-118899
RecordNVD · CVE-2026-118899
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · LLCForge/CVE-2026-118899 · Repository
Other links 1
Patchmy.f5.com · manage/s/article/K000163930

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-118899

Is CVE-2026-118899 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data

Which versions are affected by CVE-2026-118899?

NGINX Open Source: from 1.31.0 before 1.31.9; from 1.30.0 before 1.30.7; from 1.31.0. NGINX Plus: from 37.2.0.1 before 37.2.1.1; from 37.0.0 before 37.0.8.1; from R33.Source: cve.now feed data

How do I fix CVE-2026-118899?

Upgrade to a fixed version: NGINX Open Source 1.31.9, 1.30.7 · NGINX Plus 37.2.1.1, 37.0.8.1.Source: cve.now feed data

More CVEs