CVE-2026-62909

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). 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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Uncaught exception in .NET allows an authorized attacker to elevate privileges locally.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100CISA SSVC

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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-62909

Vendor Advisories for CVE-2026-62909(19)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntudotnet10 (10.0.111-10.0.11-0ubuntu1~26.04.1) @ resolute2026-10-04ubuntu
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet10.0-0:10.0.111-1.el10_22026-08-17redhat
redhatdotnet9.0-0:9.0.120-1.el9_82026-08-17redhat
redhatdotnet10.0-0:10.0.111-1.el9_82026-08-17redhat
redhatdotnet8-0-main-8.0.130-0.1.hum12026-08-16redhat
redhatdotnet10-0-main-10.0.11-1.hum12026-08-15redhat
redhatdotnet9.0-0:9.0.120-1.el8_102026-08-13redhat
redhatdotnet8.0-0:8.0.130-1.el8_102026-08-13redhat
redhatdotnet10.0-0:10.0.111-1.el8_102026-08-13redhat
redhatdotnet8.0-0:8.0.130-1.el9_82026-08-13redhat
redhatdotnet8.0-0:8.0.130-1.el10_22026-08-13redhat
redhatdotnet9.0-0:9.0.120-1.el10_22026-08-13redhat
redhatdotnet9-0-main-9.0.119-2.hum12026-07-24redhat

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

(8 across 1 ecosystem)
NuGet(8)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.NETCore.App.Runtime.linux-arm8.0.0 ... 8.0.8 (29 versions)
  • 10.0.0 up to 10.0.11: fixed in 10.0.11
  • 9.0.0 up to 9.0.19: fixed in 9.0.19
  • 8.0.0 up to 8.0.30: fixed in 8.0.30
—
Microsoft.NETCore.App.Runtime.linux-arm648.0.0 ... 8.0.8 (29 versions)
  • 10.0.0 up to 10.0.11: fixed in 10.0.11
  • 9.0.0 up to 9.0.19: fixed in 9.0.19
  • 8.0.0 up to 8.0.30: fixed in 8.0.30
—
Microsoft.NETCore.App.Runtime.linux-musl-arm8.0.0 ... 8.0.8 (29 versions)
  • 10.0.0 up to 10.0.11: fixed in 10.0.11
  • 9.0.0 up to 9.0.19: fixed in 9.0.19
  • 8.0.0 up to 8.0.30: fixed in 8.0.30
—
Microsoft.NETCore.App.Runtime.linux-musl-arm648.0.0 ... 8.0.8 (29 versions)
  • 10.0.0 up to 10.0.11: fixed in 10.0.11
  • 9.0.0 up to 9.0.19: fixed in 9.0.19
  • 8.0.0 up to 8.0.30: fixed in 8.0.30
—
Microsoft.NETCore.App.Runtime.linux-musl-x648.0.0 ... 8.0.8 (29 versions)
  • 10.0.0 up to 10.0.11: fixed in 10.0.11
  • 9.0.0 up to 9.0.19: fixed in 9.0.19
  • 8.0.0 up to 8.0.30: fixed in 8.0.30
—
Microsoft.NETCore.App.Runtime.linux-x648.0.0 ... 8.0.8 (29 versions)
  • 10.0.0 up to 10.0.11: fixed in 10.0.11
  • 9.0.0 up to 9.0.19: fixed in 9.0.19
  • 8.0.0 up to 8.0.30: fixed in 8.0.30
—
Microsoft.NETCore.App.Runtime.osx-arm648.0.0 ... 8.0.8 (29 versions)
  • 10.0.0 up to 10.0.11: fixed in 10.0.11
  • 9.0.0 up to 9.0.19: fixed in 9.0.19
  • 8.0.0 up to 8.0.30: fixed in 8.0.30
—
Microsoft.NETCore.App.Runtime.osx-x648.0.0 ... 8.0.8 (29 versions)
  • 10.0.0 up to 10.0.11: fixed in 10.0.11
  • 9.0.0 up to 9.0.19: fixed in 9.0.19
  • 8.0.0 up to 8.0.30: fixed in 8.0.30
—

Weakness Classification(2)

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 21× in last 7d / 103× 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 251 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-62909?
CVE-2026-62909 is a high vulnerability published on August 11, 2026. Uncaught exception in .NET allows an authorized attacker to elevate privileges locally.
When was CVE-2026-62909 disclosed?
CVE-2026-62909 was first published on August 11, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62909 actively exploited?
CVE-2026-62909 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62909?
CVE-2026-62909 has a CVSS base score of 7.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-62909?
A fix for CVE-2026-62909 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62909 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-62909

Explore →

Is Your Infrastructure Affected by CVE-2026-62909?

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

Book a Demo →Browse All CVEs