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.4%, top 18% 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 7.5Exploit: NoneExposed: 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)
EPSS
82.3%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 1, 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
ubuntudotnet10 (10.0.109-10.0.9-0ubuntu1~26.04.1) @ resolute2026-07-06ubuntu
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.el10_02026-06-22redhat
redhatdotnet8.0-0:8.0.128-1.el9_62026-06-22redhat
redhatdotnet9.0-0:9.0.118-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
redhatdotnet9.0-0:9.0.118-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
redhatdotnet10.0-0:10.0.109-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 30× in last 7d / 139× 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 139 total refreshes for this CVE.

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

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 July 1, 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 82.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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