CVE-2026-45491

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% 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: epss, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

Published

June 9, 2026

Last Modified

September 24, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
Patch available. Sources: microsoft.
microsoftMentions a patch (unverified)

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-45491

Patch Availability(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntudotnet10 (10.0.109-10.0.9-0ubuntu1~26.04.1) @ resolute2026-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.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
redhatdotnet8.0-0:8.0.128-1.el9_82026-06-11redhat
redhatdotnet10.0-0:10.0.109-1.el9_82026-06-11redhat
redhatdotnet9.0-0:9.0.118-1.el9_82026-06-11redhat
redhatdotnet8.0-0:8.0.128-1.el10_22026-06-10redhat
redhatdotnet9.0-0:9.0.118-1.el10_22026-06-10redhat
redhatdotnet8.0-0:8.0.128-1.el8_102026-06-10redhat
redhatdotnet10.0-0:10.0.109-1.el10_22026-06-10redhat
redhatdotnet10.0-0:10.0.109-1.el8_102026-06-10redhat
redhatdotnet9.0-0:9.0.118-1.el8_102026-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

(3 across 1 ecosystem)
NuGet(3)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.NETCore.App.Runtime.linux-x6410.0.0 ... 10.0.8 (9 versions)
  • 8.0.0 up to 8.0.28: fixed in 8.0.28
  • 9.0.0 up to 9.0.17: fixed in 9.0.17
  • 10.0.0 up to 10.0.9: fixed in 10.0.9
—
Microsoft.NETCore.App.Runtime.osx-arm6410.0.0 ... 10.0.8 (9 versions)
  • 8.0.0 up to 8.0.28: fixed in 8.0.28
  • 9.0.0 up to 9.0.17: fixed in 9.0.17
  • 10.0.0 up to 10.0.9: fixed in 10.0.9
—
Microsoft.NETCore.App.Runtime.win-x6410.0.0 ... 10.0.8 (9 versions)
  • 8.0.0 up to 8.0.28: fixed in 8.0.28
  • 9.0.0 up to 9.0.17: fixed in 9.0.17
  • 10.0.0 up to 10.0.9: fixed in 10.0.9
—

Weakness Classification(1)

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 / 25× 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 212 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45491?
CVE-2026-45491 is a medium vulnerability published on June 9, 2026. Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.
When was CVE-2026-45491 disclosed?
CVE-2026-45491 was first published on June 9, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45491 actively exploited?
CVE-2026-45491 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45491?
CVE-2026-45491 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45491?
A fix for CVE-2026-45491 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45491 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-45491

Explore →

Is Your Infrastructure Affected by CVE-2026-45491?

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