{"uuid": "70019254-e207-4a71-901c-dbd6db6ed851", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-62897", "type": "seen", "source": "https://gist.github.com/alon710/64a84b16b48a0327d43d9cf3f2891634", "content": "# CVE-2026-62897: CVE-2026-62897: Integer Overflow and Code Execution in .NET WPF and WinForms\n\n> **CVSS Score:** 7.0\n> **Published:** 2026-08-11\n> **Full Report:** https://cvereports.com/reports/CVE-2026-62897\n\n## Summary\nAn integer overflow vulnerability (CWE-190) exists in the layout and rendering engines of the Microsoft .NET Framework and .NET Core. This flaw resides within the processing of complex coordinate maps, font tables, and image metadata in Windows Presentation Foundation (WPF) and Windows Forms (WinForms). By convincing a user to open a crafted vector graphic or layout document, a local attacker can exploit this arithmetic error to induce an undersized memory allocation, leading to a heap-based buffer overflow and subsequent arbitrary code execution within the context of the vulnerable application.\n\n## TL;DR\nAn integer overflow in .NET's WPF and WinForms rendering components allows local attackers to execute arbitrary code via malformed layout or graphic data.\n\n## Technical Details\n\n- **CWE ID**: CWE-190 (Integer Overflow or Wraparound)\n- **Attack Vector**: Local (AV:L)\n- **CVSS v3.1 Score**: 7.0 (High)\n- **Exploit Status**: None (No public exploits or PoCs available)\n- **KEV Status**: Not listed in CISA Known Exploited Vulnerabilities catalog\n- **Primary Impact**: Local Arbitrary Code Execution\n\n## Affected Systems\n\n- Microsoft .NET 10.0\n- Microsoft .NET 9.0\n- Microsoft .NET 8.0\n- Microsoft .NET Framework 3.5\n- Microsoft .NET Framework 4.7.2\n- Microsoft .NET Framework 4.8\n- Microsoft .NET Framework 4.8.1\n- Microsoft Visual Studio 2022\n- Microsoft Visual Studio 2026\n- **.NET**: 10.0.0 to < 10.0.11 (Fixed in: `10.0.11`)\n- **.NET**: 9.0.0 to < 9.0.19 (Fixed in: `9.0.19`)\n- **.NET**: 8.0.0 to < 8.0.30 (Fixed in: `8.0.30`)\n- **Visual Studio 2022**: 17.14.0 to < 17.14.38 (Fixed in: `17.14.38`)\n- **Visual Studio 2026**: 18.0 to < 18.8.3 (Fixed in: `18.8.3`)\n\n## Mitigation\n\n- Apply Microsoft's official servicing security updates for .NET, .NET Framework, and Visual Studio\n- Validate dimensions and scale factors of user-supplied assets before processing them in drawing contexts\n- Use safe integer libraries or checked contexts in custom math logic to prevent arithmetic overflows\n\n**Remediation Steps:**\n1. Identify all deployed versions of .NET, .NET Framework, and Visual Studio in the environment\n2. Apply Microsoft's August 2026 security updates to bring the components to the fixed versions\n3. For custom applications, wrap potentially unsafe coordinate math in checked blocks to catch overflows\n\n## References\n\n- [Microsoft MSRC Security Update Guide for CVE-2026-62897](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62897)\n- [Official CVE Record (CVE.org)](https://www.cve.org/CVERecord?id=CVE-2026-62897)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-62897) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-08-11T22:32:27.220656Z"}