CVE-2026-123007

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-128949 (ENISA EUVD) · GHSA-m4q8-cf44-f42r (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: 30%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.

Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. 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
30%
EPSS %ILE
98th
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
30% 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-light (1.18.0-0ubuntu1.7+esm5) @ focal2026-11-19ubuntu

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

Weakness Classification(2)

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 30% · 98th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 6.0% · 93rd percentile
  3. 2026-11-20 16:27 UTCVendor advisory
  4. 2026-11-20 16:27 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  5. 2026-11-20 12:28 UTCEchelonGraph re-scored
  6. 2026-11-20 12:28 UTCVendor advisory
  7. 2026-11-20 12:28 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  8. 2026-11-20 11:23 UTCEchelonGraph re-scored
  9. 2026-11-20 11:23 UTCVendor advisory
  10. 2026-11-20 11:23 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  11. 2026-11-20 01:17 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  12. 2026-11-19 21:28 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  13. 2026-11-19 18:48 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  14. 2026-11-19 16:44 UTCEchelonGraph re-scored
  15. 2026-11-19 16:44 UTCVendor advisory
  16. 2026-11-19 16:44 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  17. 2026-11-19 16:33 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
  18. 2026-11-19 16:26 UTCVendor advisory
  19. 2026-11-19 16:26 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  20. 2026-11-19 06:28 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  21. 2026-11-19 05:28 UTCEchelonGraph re-scored
  22. 2026-11-19 05:28 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  23. 2026-11-19 05:04 UTCEchelonGraph re-scored
  24. 2026-11-19 05:04 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  25. 2026-11-18 21:28 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
Show 12 more
  1. 2026-11-18 20:28 UTCEchelonGraph re-scored
  2. 2026-11-18 20:28 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  3. 2026-11-18 20:18 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  4. 2026-11-18 19:43 UTCEchelonGraph re-scored
  5. 2026-11-18 19:43 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  6. 2026-11-18 18:47 UTCEchelonGraph re-scored
  7. 2026-11-18 18:47 UTCGHSA enrichmentGHSA-m4q8-cf44-f42r · GitHub severity CRITICAL · GitHub CVSS 8.1
  8. 2026-11-18 17:28 UTCEchelonGraph re-scored
  9. 2026-11-18 16:21 UTCEchelonGraph re-scored
  10. 2026-11-18 16:03 UTCENISA EUVD ID recordedEUVD-2026-128949 · Source: ENISA EUVD
  11. 2026-11-18 15:28 UTCEchelonGraph re-scoredFirst assessed: 8.1 HIGH
  12. 2026-11-18 15:27 UTCMITRE cvelistV5first tracked

Publicly available exploits

(9 references)

Public exploit code is referenced for this CVE (8 GitHub PoCs), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoC0xcypher110/nginx2root_lab
    Published Nov 19, 2026

    Docker-based reproduction of CVE-2026-123007

    Open source ↗
  • GitHub PoCakarkode/nginx-http2-cve-2026-123007-lab
    Published Nov 19, 2026

    Local lab for CVE-2026-123007 (nginx HTTP/2 integer underflow): vulnerable Docker container + proof-of-concept

    Open source ↗
  • GitHub PoCfoxcornlab/nginx-scanner
    Published Nov 19, 2026

    Detection-only triage for nginx2root — CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425 (CVSS 4.0 9.2) + CVE-2026-118899 — grades nginx 1.30.7 / 1.31.9 fixes, probes HTTP/2, HTTP/3, resolver, mail proxy and TLS 1.3 exposure. No payloads.

    Open source ↗
  • GitHub PoCHOSTED-POWER/nginx2root-patches
    Published Nov 19, 2026

    Fully patched builds of the distributions' own nginx for nginx2root (CVE-2026-123007) and 11 more CVEs: Debian 8-13, CentOS 7/8, RHEL and Rocky Linux 8/9/10, Oracle Linux 9/10. Same packages, modules and config; HTTP/2 stays on; the official update takes over automatically.

    Open source ↗
  • GitHub PoCMahgal/nginx-http2-rce-check
    Published Nov 19, 2026

    Answer 'am I exposed to the Nginx HTTP/2 RCE?' in one command — check your nginx version and HTTP/2 config against CVE-2026-123007 / CVE-2026-123633 (disclosed 2026-11-18, CVSS 9.2).

    Open source ↗
  • GitHub checkerThe-DevOps-Daily/nginx2root-check
    Published Nov 18, 2026

    Read-only checker for the five nginx2root CVEs (CVE-2026-123007/123633/121810/123634/113425), fixed in nginx 1.31.9 and 1.30.7

    Open source ↗
  • GitHub PoCarkrwn/NGINX2Root-CVE-2026-123007
    Published Nov 18, 2026

    Research Note: Turning Public Intelligence into a Root Exploit (Case Study: CVE-2026-123007)

    Open source ↗
  • GitHub PoCsfewer-r7/CVE-2026-123007
    Published Nov 18, 2026

    Proof-of-concept (PoC) scripts for CVE-2026-123007, an integer underflow in NGINX HTTP/2.

    Open source ↗
  • GitHub PoCWormW/nginx2root-rce-lab
    Published Nov 18, 2026

    CVE-2026-123007(nginx2root)RCE 复现 + 未标定 nginx 版本标定工具

    Open source ↗

Frequently asked(5)

What is CVE-2026-123007?
CVE-2026-123007 is a high-severity vulnerability; its CVE record was published on November 18, 2026. This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault.…
When was CVE-2026-123007 made public?
CVE-2026-123007 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-123007 actively exploited?
CVE-2026-123007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-123007?
CVE-2026-123007 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-123007?
A fix for CVE-2026-123007 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-123007 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-123007?

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