CVE-2026-45591

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 2.5%, top 16% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:microsoft, epss
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Uncontrolled resource consumption in ASP.NET Core allows an unauthorized attacker to deny service over a network.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

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
Severity75% × 45%
Exploitation2% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
84%
KEV
Not listed

Published

June 9, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jun 10, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

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

Vendor Advisories for CVE-2026-45591(18)

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

Patch Availability(18)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunetstandard-targeting-pack-2.1-8.0 (8.0.128-0ubuntu1~24.04.1) @ noble2026-09-14ubuntu
redhatdotnet9.0-0:9.0.118-1.el9_62026-06-29redhat
redhatdotnet8.0-0:8.0.128-1.el9_42026-06-23redhat
redhatdotnet8.0-0:8.0.128-1.el9_62026-06-22redhat
redhatdotnet9.0-0:9.0.118-1.el10_02026-06-22redhat
redhatdotnet8.0-0:8.0.128-1.el10_02026-06-22redhat
redhatdotnet8-0-main-8.0.128-1.hum12026-06-18redhat
redhatdotnet10-0-main-10.0.109-1.hum12026-06-17redhat
redhatdotnet10.0-0:10.0.109-1.el9_82026-06-11redhat
redhatdotnet8.0-0:8.0.128-1.el9_82026-06-11redhat
redhatdotnet9.0-0:9.0.118-1.el9_82026-06-11redhat
redhatdotnet10.0-0:10.0.109-1.el10_22026-06-10redhat
redhatdotnet8.0-0:8.0.128-1.el8_102026-06-10redhat
redhatdotnet9.0-0:9.0.118-1.el8_102026-06-10redhat
redhatdotnet10.0-0:10.0.109-1.el8_102026-06-10redhat
redhatdotnet8.0-0:8.0.128-1.el10_22026-06-10redhat
redhatdotnet9.0-0:9.0.118-1.el10_22026-06-10redhat
redhatdotnet9-0-main-9.0.117-1.hum12026-05-14redhat

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

(4 across 1 ecosystem)
NuGet(4)
PackageVulnerable rangeFixed inDependents
Microsoft.AspNetCore.App.Runtime.linux-x6410.0.0 ... 10.0.8 (9 versions)10.0.9—
Microsoft.AspNetCore.App.Runtime.osx-arm6410.0.0 ... 10.0.8 (9 versions)10.0.9—
Microsoft.AspNetCore.App.Runtime.win-x6410.0.0 ... 10.0.8 (9 versions)10.0.9—
Microsoft.AspNetCore.SignalR.Protocols.MessagePack10.0.0 ... 10.0.8 (9 versions)10.0.9—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

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 7× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 249 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45591?
CVE-2026-45591 is a high vulnerability published on June 9, 2026. Uncontrolled resource consumption in ASP.NET Core allows an unauthorized attacker to deny service over a network.
When was CVE-2026-45591 disclosed?
CVE-2026-45591 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45591 actively exploited?
CVE-2026-45591 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 16.2% of all scored CVEs.
What is the CVSS score of CVE-2026-45591?
CVE-2026-45591 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45591?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45591, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-45591?

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

Start Free Scan →Browse All CVEs