CVE-2026-62902

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.9% (57th 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Inclusion of functionality from untrusted control sphere in .NET allows an unauthorized attacker to disclose information over a network.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
30
EG Risk 30/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
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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-62902

Vendor Advisories for CVE-2026-62902(4)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdotnet8-0-main-8.0.130-0.1.hum12026-08-16redhat
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

(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(3)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 70× 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 181 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-62902?
CVE-2026-62902 is a medium vulnerability published on August 11, 2026. Inclusion of functionality from untrusted control sphere in .NET allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-62902 disclosed?
CVE-2026-62902 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-62902 actively exploited?
CVE-2026-62902 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62902?
CVE-2026-62902 has a CVSS base score of 6.5 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-62902?
A fix for CVE-2026-62902 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62902 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-62902

Explore →

Is Your Infrastructure Affected by CVE-2026-62902?

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

Book a Demo →Browse All CVEs