CVE-2026-62886

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.5% (38th 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.5%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Integer overflow or wraparound in .NET allows an unauthorized 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.5%
EPSS %ILE
38th
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-62886

Vendor Advisories for CVE-2026-62886(2)

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

Affected Packages

(3 across 1 ecosystem)
NuGet(3)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.WindowsDesktop.App.Runtime.win-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.WindowsDesktop.App.Runtime.win-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.WindowsDesktop.App.Runtime.win-x868.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.

Data Freshness Timeline

(refreshed 20× in last 7d / 94× 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 233 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-62886?
CVE-2026-62886 is a high vulnerability published on August 11, 2026. Integer overflow or wraparound in .NET allows an unauthorized attacker to elevate privileges locally.
When was CVE-2026-62886 disclosed?
CVE-2026-62886 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-62886 actively exploited?
CVE-2026-62886 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62886?
CVE-2026-62886 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-62886?
A fix for CVE-2026-62886 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62886 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-62886

Explore →

Is Your Infrastructure Affected by CVE-2026-62886?

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

Book a Demo →Browse All CVEs