CVE-2026-120796

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.2% (67th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.6 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-11-10) is not newer than that change (2026-11-12), so it does not.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory

Also known asEUVD-2026-122469 (ENISA EUVD) · GHSA-cpw3-h88j-9f6x (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Inefficient algorithmic complexity in .NET allows an unauthorized attacker to deny service over a network.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.2% × 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
1.2%
EPSS %ILE
67th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
1.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 10, 2026

Last Modified

November 12, 2026

Vendor Advisories for CVE-2026-120796(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntudotnet11 (11.0.100-11.0.0-0ubuntu1~26.10.1) @ stonking2026-11-12ubuntu
nugetMicrosoft.NETCore.App.Runtime.linux-arm @ 11.0.0 (fixes >= 11.0.0-preview.1.26104.118, <= 11.0.0-rc.3.26522.148)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 1 ecosystem)
NuGet(12)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.NETCore.App.Runtime.linux-arm—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.linux-arm64—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.linux-musl-arm—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.linux-musl-arm64—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.linux-musl-x64—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.linux-x64—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.osx-arm64—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.osx-x64—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.win-arm64—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.win-x64—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
Microsoft.NETCore.App.Runtime.win-x86—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—
System.Text.Json—
  • 11.0.0-preview.1.26104.118 up to 11.0.0: fixed in 11.0.0
—

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 13× in last 7d / 13× 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-12 22:01 UTCEchelonGraph re-scored
  2. 2026-11-12 22:01 UTCGHSA enrichmentGHSA-cpw3-h88j-9f6x · GitHub severity MODERATE · GitHub CVSS 4.6
  3. 2026-11-12 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  4. 2026-11-12 15:58 UTCEchelonGraph re-scored
  5. 2026-11-12 15:58 UTCVendor advisory
  6. 2026-11-12 15:58 UTCGHSA enrichmentGHSA-cpw3-h88j-9f6x · GitHub severity MODERATE · GitHub CVSS 4.6
  7. 2026-11-11 17:31 UTCEchelonGraph re-scored
  8. 2026-11-11 17:31 UTCVendor advisory
  9. 2026-11-11 17:31 UTCGHSA enrichmentGHSA-cpw3-h88j-9f6x · GitHub severity MODERATE · GitHub CVSS 4.6
  10. 2026-11-11 16:38 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  11. 2026-11-11 02:31 UTCEchelonGraph re-scored
  12. 2026-11-11 02:31 UTCVendor advisory
  13. 2026-11-11 02:31 UTCGHSA enrichmentGHSA-cpw3-h88j-9f6x · GitHub severity MODERATE · GitHub CVSS 4.6
  14. 2026-11-11 01:45 UTCEchelonGraph re-scored
  15. 2026-11-11 01:45 UTCGHSA enrichmentGHSA-cpw3-h88j-9f6x · GitHub severity MODERATE · GitHub CVSS 4.6
  16. 2026-11-11 00:06 UTCEchelonGraph re-scored
  17. 2026-11-11 00:06 UTCGHSA enrichmentGHSA-cpw3-h88j-9f6x · GitHub severity MODERATE · GitHub CVSS 4.6
  18. 2026-11-10 19:42 UTCEchelonGraph re-scored
  19. 2026-11-10 19:10 UTCENISA EUVD ID recordedEUVD-2026-122469 · Source: ENISA EUVD
  20. 2026-11-10 18:31 UTCEchelonGraph re-scoredFirst assessed: 5.3 MEDIUM
  21. 2026-11-10 18:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-120796?
CVE-2026-120796 is a medium-severity vulnerability; its CVE record was published on November 10, 2026. Inefficient algorithmic complexity in .NET allows an unauthorized attacker to deny service over a network.
When was CVE-2026-120796 made public?
CVE-2026-120796 was made public on November 10, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on November 10, 2026. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-120796 actively exploited?
CVE-2026-120796 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-120796?
CVE-2026-120796 has a CVSS base score of 5.3 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-120796?
A fix for CVE-2026-120796 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-120796 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-120796

Explore →

Is Your Infrastructure Affected by CVE-2026-120796?

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