CVE-2026-56170

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.2% (66th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 sources updated this week
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: 1.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.

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

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
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
66th
KEV
Not listed

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.

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

July 14, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-56170

Vendor Advisories for CVE-2026-56170(19)

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

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet10.0-0:10.0.110-1.el9_82026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el9_82026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el9_82026-07-20redhat
redhatdotnet8-0-main-8.0.129-2.1.hum12026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el10_22026-07-20redhat
redhatdotnet9-0-main-9.0.119-1.hum12026-07-15redhat
redhatdotnet10-0-main-10.0.109-1.hum12026-06-17redhat

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.AspNetCore.App.Runtime.linux-arm8.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.linux-arm648.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.linux-musl-arm8.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.linux-musl-arm648.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.linux-musl-x648.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.linux-x648.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.osx-arm648.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.osx-x648.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.win-arm—
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.win-arm648.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.win-x648.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—
Microsoft.AspNetCore.App.Runtime.win-x868.0.0 ... 8.0.8 (25 versions)
  • 10.0.0 up to 10.0.6: fixed in 10.0.6
  • 9.0.0 up to 9.0.15: fixed in 9.0.15
  • 8.0.0 up to 8.0.26: fixed in 8.0.26
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 43× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 247 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 147 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:53 UTCEG score recompute
  6. 2026-10-11 14:16 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  10. 2026-10-08 18:28 UTCEG score recompute
  11. 2026-10-08 18:28 UTCVendor advisory
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  20. 2026-10-01 13:17 UTCEG score recompute
  21. 2026-10-01 13:17 UTCVendor advisory
  22. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  23. 2026-09-29 15:22 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  24. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  25. 2026-09-28 09:17 UTCEG score recompute
Show 75 more
  1. 2026-09-28 09:17 UTCVendor advisory
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  4. 2026-09-25 19:10 UTCEG score recompute
  5. 2026-09-25 19:10 UTCVendor advisory
  6. 2026-09-24 14:04 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  7. 2026-09-24 09:21 UTCEG score recompute
  8. 2026-09-24 09:21 UTCVendor advisory
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  10. 2026-09-23 03:52 UTCEG score recompute
  11. 2026-09-23 03:52 UTCVendor advisory
  12. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  13. 2026-09-17 23:18 UTCEG score recompute
  14. 2026-09-17 23:18 UTCVendor advisory
  15. 2026-09-17 19:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  16. 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  18. 2026-09-15 03:11 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-09-14 11:36 UTCVendor advisory
  20. 2026-09-13 23:25 UTCEG score recompute
  21. 2026-09-13 23:25 UTCVendor advisory
  22. 2026-09-13 16:47 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-09-13 07:51 UTCEG score recompute
  24. 2026-09-13 07:51 UTCVendor advisory
  25. 2026-09-12 13:52 UTCVendor advisory
  26. 2026-09-12 01:42 UTCEG score recompute
  27. 2026-09-12 01:42 UTCVendor advisory
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  29. 2026-09-10 09:35 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  30. 2026-09-09 22:54 UTCVendor advisory
  31. 2026-09-08 22:49 UTCEG score recompute
  32. 2026-09-08 22:49 UTCVendor advisory
  33. 2026-09-08 22:01 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  34. 2026-09-08 01:39 UTCEG score recompute
  35. 2026-09-08 01:39 UTCVendor advisory
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  38. 2026-09-06 13:44 UTCVendor advisory
  39. 2026-09-05 21:15 UTCEG score recompute
  40. 2026-09-05 21:15 UTCVendor advisory
  41. 2026-09-04 23:21 UTCEG score recompute
  42. 2026-09-04 23:21 UTCVendor advisory
  43. 2026-09-04 05:07 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  44. 2026-09-02 19:55 UTCEG score recompute
  45. 2026-09-02 19:55 UTCVendor advisory
  46. 2026-09-02 14:12 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  48. 2026-09-01 04:40 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  49. 2026-08-31 16:11 UTCVendor advisory
  50. 2026-08-31 05:33 UTCEG score recompute
  51. 2026-08-31 05:33 UTCVendor advisory
  52. 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  53. 2026-08-30 17:23 UTCVendor advisory
  54. 2026-08-30 05:14 UTCEG score recompute
  55. 2026-08-30 05:14 UTCVendor advisory
  56. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  57. 2026-08-28 23:29 UTCEG score recompute
  58. 2026-08-28 23:29 UTCVendor advisory
  59. 2026-08-28 21:41 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  60. 2026-08-28 02:28 UTCEG score recompute
  61. 2026-08-28 02:28 UTCVendor advisory
  62. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  63. 2026-08-27 14:07 UTCVendor advisory
  64. 2026-08-27 01:57 UTCEG score recompute
  65. 2026-08-27 01:57 UTCVendor advisory
  66. 2026-08-26 14:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  67. 2026-08-26 13:48 UTCVendor advisory
  68. 2026-08-26 01:38 UTCEG score recompute
  69. 2026-08-26 01:38 UTCVendor advisory
  70. 2026-08-25 13:49 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  71. 2026-08-25 09:31 UTCVendor advisory
  72. 2026-08-24 21:17 UTCVendor advisory
  73. 2026-08-24 19:47 UTCEG score recompute
  74. 2026-08-24 19:47 UTCVendor advisory
  75. 2026-08-24 06:26 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56170?
CVE-2026-56170 is a high-severity vulnerability; its CVE record was published on July 14, 2026. Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.
When was CVE-2026-56170 made public?
CVE-2026-56170 was made public on July 14, 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 July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-56170 actively exploited?
CVE-2026-56170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56170?
CVE-2026-56170 has a CVSS base score of 7.5 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-56170?
A fix for CVE-2026-56170 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56170 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-56170

Explore →

Is Your Infrastructure Affected by CVE-2026-56170?

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

Book a Demo →Browse All CVEs