CVE-2026-62897

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Integer overflow or wraparound in .NET Framework allows an unauthorized attacker to execute code locally.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 20, 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-62897

Vendor Advisories for CVE-2026-62897(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 rangeFixed inDependents
Microsoft.WindowsDesktop.App.Runtime.win-arm6410.0.0 ... 10.0.9 (11 versions)10.0.11—
Microsoft.WindowsDesktop.App.Runtime.win-x6410.0.0 ... 10.0.9 (11 versions)10.0.11—
Microsoft.WindowsDesktop.App.Runtime.win-x8610.0.0 ... 10.0.9 (11 versions)10.0.11—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 47× in last 7d / 81× 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.

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

Frequently asked(5)

What is CVE-2026-62897?
CVE-2026-62897 is a high vulnerability published on August 11, 2026. Integer overflow or wraparound in .NET Framework allows an unauthorized attacker to execute code locally.
When was CVE-2026-62897 disclosed?
CVE-2026-62897 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62897 actively exploited?
CVE-2026-62897 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.1% of all scored CVEs.
What is the CVSS score of CVE-2026-62897?
CVE-2026-62897 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-62897?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62897, 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-62897

Explore →

Is Your Infrastructure Affected by CVE-2026-62897?

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

Start Free Scan →Browse All CVEs