CVE-2026-118899

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-18. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-128946 (ENISA EUVD) · GHSA-mjqw-rmmf-hgxf (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
3.8%
EPSS %ILE
90th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
3.8% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 19, 2026

Advisory Details (1)

Auto-updated Nov 18, 2026
Patch available.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunginx-light (1.14.0-0ubuntu1.11+esm6) @ bionic2026-11-19ubuntu

These rows come from Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 3.8% · 90th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  3. 2026-11-20 01:00 UTCGHSA enrichmentGHSA-mjqw-rmmf-hgxf · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-19 19:48 UTCVendor advisory
  5. 2026-11-19 19:48 UTCGHSA enrichmentGHSA-mjqw-rmmf-hgxf · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-19 19:09 UTCGHSA enrichmentGHSA-mjqw-rmmf-hgxf · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-11-19 18:09 UTCEchelonGraph re-scored
  8. 2026-11-19 18:09 UTCGHSA enrichmentGHSA-mjqw-rmmf-hgxf · GitHub severity HIGH · GitHub CVSS 7.5
  9. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  10. 2026-11-18 18:47 UTCEchelonGraph re-scored
  11. 2026-11-18 18:47 UTCGHSA enrichmentGHSA-mjqw-rmmf-hgxf · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-18 17:28 UTCEchelonGraph re-scored
  13. 2026-11-18 16:53 UTCEchelonGraph re-scored
  14. 2026-11-18 16:28 UTCEchelonGraph re-scored
  15. 2026-11-18 16:03 UTCENISA EUVD ID recordedEUVD-2026-128946 · Source: ENISA EUVD
  16. 2026-11-18 15:28 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  17. 2026-11-18 15:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-118899?
CVE-2026-118899 is a high-severity vulnerability; its CVE record was published on November 18, 2026. 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…
When was CVE-2026-118899 made public?
CVE-2026-118899 was made public on November 18, 2026: that is the date its CVE record's CNA, F5, Inc., gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2026. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-118899 actively exploited?
CVE-2026-118899 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.8% probability of exploitation in the next 30 days (90th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118899?
CVE-2026-118899 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118899?
A fix for CVE-2026-118899 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118899 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-118899 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-118899

Explore →

Is Your Infrastructure Affected by CVE-2026-118899?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.