CVE-2026-123633

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-128944 (ENISA EUVD) · GHSA-7xxj-p8w5-434q (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 18%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request can result in use-after-free in the worker process, if this process is running low on worker_connections. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.

Impact:

This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or may allow a code execution. 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
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
18%
EPSS %ILE
97th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
18% 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 20, 2026

Advisory Details (1)

Auto-updated Nov 18, 2026
Patch available.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnginx-2:1.26.3-16.el10_3.32026-11-20redhat
ubuntunginx-naxsi-ui (1.4.6-1ubuntu3.9+esm10) @ trusty2026-11-19ubuntu

These rows come from Red Hat and 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.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 26× in last 7d / 26× 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 18% · 97th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  3. 2026-11-20 12:28 UTCEchelonGraph re-scored
  4. 2026-11-20 12:28 UTCVendor advisory
  5. 2026-11-20 12:28 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  6. 2026-11-20 11:23 UTCEchelonGraph re-scored
  7. 2026-11-20 11:23 UTCVendor advisory
  8. 2026-11-20 11:23 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  9. 2026-11-20 01:17 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  10. 2026-11-19 21:48 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  11. 2026-11-19 18:28 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  12. 2026-11-19 16:44 UTCEchelonGraph re-scored
  13. 2026-11-19 16:44 UTCVendor advisory
  14. 2026-11-19 16:44 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  15. 2026-11-19 16:33 UTCEPSS rescoreEPSS 6.5% · 93rd percentile
  16. 2026-11-19 16:26 UTCVendor advisory
  17. 2026-11-19 16:26 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  18. 2026-11-19 06:28 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  19. 2026-11-19 05:28 UTCEchelonGraph re-scored
  20. 2026-11-19 05:28 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  21. 2026-11-19 05:04 UTCEchelonGraph re-scored
  22. 2026-11-19 05:04 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  23. 2026-11-18 23:28 UTCEchelonGraph re-scored
  24. 2026-11-18 23:28 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  25. 2026-11-18 22:24 UTCEchelonGraph re-scored
Show 15 more
  1. 2026-11-18 22:24 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  2. 2026-11-18 21:28 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  3. 2026-11-18 20:28 UTCEchelonGraph re-scored
  4. 2026-11-18 20:28 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  5. 2026-11-18 19:58 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  6. 2026-11-18 19:34 UTCEchelonGraph re-scored
  7. 2026-11-18 19:34 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  8. 2026-11-18 18:47 UTCEchelonGraph re-scored
  9. 2026-11-18 18:47 UTCGHSA enrichmentGHSA-7xxj-p8w5-434q · GitHub severity CRITICAL · GitHub CVSS 8.1
  10. 2026-11-18 17:28 UTCEchelonGraph re-scored
  11. 2026-11-18 16:58 UTCEchelonGraph re-scored
  12. 2026-11-18 16:28 UTCEchelonGraph re-scored
  13. 2026-11-18 16:03 UTCENISA EUVD ID recordedEUVD-2026-128944 · Source: ENISA EUVD
  14. 2026-11-18 15:28 UTCEchelonGraph re-scoredFirst assessed: 8.1 HIGH
  15. 2026-11-18 15:27 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCGhost-Bx1/nginx-exploits
    Published Nov 18, 2026

    Exploits e PoCs para vulnerabilidades no NGINX - CVE-2026-123633, CVE-2026-123007

    Open source ↗

Frequently asked(5)

What is CVE-2026-123633?
CVE-2026-123633 is a high-severity vulnerability; its CVE record was published on November 18, 2026. When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request can result in use-after-free in the worker process, if this process is running low on worker_connections. Additionally, attackers can execute…
When was CVE-2026-123633 made public?
CVE-2026-123633 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 20, 2026; the record at its source may have been updated since.
Is CVE-2026-123633 actively exploited?
CVE-2026-123633 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-123633?
CVE-2026-123633 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-123633?
A fix for CVE-2026-123633 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-123633 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-123633?

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