CVE-2026-107494

CRITICALPre-NVD 7.59.1
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-128601 (ENISA EUVD) · GHSA-9x26-7724-x23j (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames.

Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition.

FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary.

CVSS v3
7.5
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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
0.4%
EPSS %ILE
33rd
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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 20, 2026

Advisory Details (1)

Auto-updated Nov 19, 2026
Patch available. Sources: github_pr.
GitHub pull request

CVE-2026-107494 QUIC: follow up on unbounded RETIRE_CONNECTION_ID backlog (memory DoS)

Upstream fix in progress (PR #33544 · openssl/openssl, state=open)

https://github.com/openssl/openssl/pull/33544

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatruby3-3-main-3.3.13-23.8.hum12026-10-24redhat
redhatruby3-4-main-3.4.12-33.1.hum12026-10-23redhat
redhatpython-cryptography-main-50.0.0-1.1.hum12026-10-12redhat
redhatrust-bootupd-main-0.3.2-1.1.hum12026-10-12redhat
redhatchunkah-main-0.7.1-1.hum12026-10-08redhat

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

Data Freshness Timeline

(refreshed 16× in last 7d / 16× 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 21:45 UTCEchelonGraph re-scored
  2. 2026-11-21 21:45 UTCVendor advisory
  3. 2026-11-21 21:45 UTCGHSA enrichmentGHSA-9x26-7724-x23j · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-11-20 19:28 UTCGHSA enrichmentGHSA-9x26-7724-x23j · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-11-20 18:22 UTCEchelonGraph re-scored
  7. 2026-11-20 18:22 UTCGHSA enrichmentGHSA-9x26-7724-x23j · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-11-20 18:21 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  9. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-11-20 11:28 UTCGHSA enrichmentGHSA-9x26-7724-x23j · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-11-20 11:03 UTCEchelonGraph re-scored
  12. 2026-11-20 11:03 UTCGHSA enrichmentGHSA-9x26-7724-x23j · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-11-19 22:29 UTCGHSA enrichmentGHSA-9x26-7724-x23j
  14. 2026-11-19 21:24 UTCEchelonGraph re-scoredFirst assessed: 9.1 CRITICAL
  15. 2026-11-19 21:24 UTCGHSA enrichmentGHSA-9x26-7724-x23j
  16. 2026-11-19 21:22 UTCMITRE cvelistV5CVSS → 9.1 · severity → CRITICAL
  17. 2026-11-19 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-11-18 13:03 UTCENISA EUVD ID recordedEUVD-2026-128601 · Source: ENISA EUVD
  19. 2026-11-18 12:50 UTCGHSA enrichmentGHSA-9x26-7724-x23j
  20. 2026-11-18 11:48 UTCEchelonGraph re-scored
  21. 2026-11-18 11:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-107494?
CVE-2026-107494 is a critical-severity vulnerability; its CVE record was published on November 18, 2026. Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory…
When was the CVE record for CVE-2026-107494 published?
The CVE record for CVE-2026-107494 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-107494 actively exploited?
CVE-2026-107494 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107494?
CVE-2026-107494 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises CISA-ADP (Vulnrichment) CVSS v3.1 + FIRST EPSS + GHSA into a combined EG score of 9.1 (CRITICAL).
How do I remediate CVE-2026-107494?
A fix for CVE-2026-107494 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107494 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-107494?

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