Is CVE-2026-62886 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-62886 being exploited in the wild.

How severe is CVE-2026-62886?

High severity, with a CVSS score of 7.8, published 11 August 2026.

Which products and versions are affected?

Microsoft Windows Presentation Foundation (WPF) 8.0.0 to 8.0.29, 9.0.0 to 9.0.18, 10.0.0 to 10.0.10; Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet) ECOSYSTEM:introduced=10.0.0,fixed=10.0.11; Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet) ECOSYSTEM:introduced=10.0.0,fixed=10.0.11; Microsoft.WindowsDesktop.App.Runtime.win-x86 (NuGet) ECOSYSTEM:introduced=10.0.0,fixed=10.0.11.

Is there a fix for CVE-2026-62886?

Yes. Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): upgrade to 10.0.11 or later; Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): upgrade to 10.0.11 or later; Microsoft.WindowsDesktop.App.Runtime.win-x86 (NuGet): upgrade to 10.0.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-62886 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-62886?

Check whether you run Microsoft .Net, Microsoft Visual Studio 2022, Microsoft Visual Studio 2026 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-62886: Integer overflow or wraparound in .NET allows an unauthorized attacker to elevate privileges locally.

CVE-2026-62886 · Severity: high · CVSS 7.8 · Published 2026-08-11

A security vulnerability has been identified in Microsoft's Windows Presentation Foundation (WPF), a framework used for building Windows desktop applications. An attacker could exploit this flaw to gain higher-level system permissions on a local machine, potentially allowing them to access sensitive data or modify system settings. This issue requires a user to perform a specific action, such as opening a malicious file, to trigger the exploit. Organizations should update their .NET runtimes and recompile any self-contained applications to mitigate this risk.

Technologies: Microsoft .Net, Microsoft Visual Studio 2022, Microsoft Visual Studio 2026, Microsoft Windows, Microsoft Windows Presentation Foundation (WPF), Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet), Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet), Microsoft.WindowsDesktop.App.Runtime.win-x86 (NuGet). Vendors: Microsoft, NuGet.

Quick answers

Is CVE-2026-62886 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62886 being exploited in the wild.
How severe is CVE-2026-62886?: High severity, with a CVSS score of 7.8, published 11 August 2026.
Which products and versions are affected?: Microsoft Windows Presentation Foundation (WPF) 8.0.0 to 8.0.29, 9.0.0 to 9.0.18, 10.0.0 to 10.0.10; Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet) ECOSYSTEM:introduced=10.0.0,fixed=10.0.11; Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet) ECOSYSTEM:introduced=10.0.0,fixed=10.0.11; Microsoft.WindowsDesktop.App.Runtime.win-x86 (NuGet) ECOSYSTEM:introduced=10.0.0,fixed=10.0.11.
Is there a fix for CVE-2026-62886?: Yes. Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): upgrade to 10.0.11 or later; Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): upgrade to 10.0.11 or later; Microsoft.WindowsDesktop.App.Runtime.win-x86 (NuGet): upgrade to 10.0.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-62886 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-62886?: Check whether you run Microsoft .Net, Microsoft Visual Studio 2022, Microsoft Visual Studio 2026 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): upgrade to 10.0.11 or later

dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-arm64 --version 10.0.11

Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): upgrade to 10.0.11 or later

dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-x64 --version 10.0.11

Microsoft.WindowsDesktop.App.Runtime.win-x86 (NuGet): upgrade to 10.0.11 or later

dotnet add package Microsoft.WindowsDesktop.App.Runtime.win-x86 --version 10.0.11

Technical details

A vulnerability exists in Windows Presentation Foundation (WPF) within .NET 8, 9, and 10 due to an integer overflow (CWE-190) that leads to a heap-based buffer overflow (CWE-122). The flaw is triggered when the application performs calculations that result in a wraparound, allowing an attacker to overwrite memory in the heap. While the attack vector is local, it requires no prior privileges (PR:N) but does necessitate user interaction (UI:R). Successful exploitation allows an unauthorized attacker to elevate their privileges on the local system. Microsoft has released patches for .NET 8 (8.0.30), .NET 9 (9.0.19), and .NET 10 (10.0.11). Developers using self-contained deployments must recompile and redeploy their applications.

Affected products

Microsoft Windows Presentation Foundation (WPF) 8.0.0 to 8.0.29, 9.0.0 to 9.0.18, 10.0.0 to 10.0.10
Microsoft .NET 8.0, 9.0, 10.0

Identifiers

CVE-2026-62886
GHSA-jqhp-238x-qhgf

Timeline

2026-08-11: disclosed
2026-08-11: advisory
2026-08-11: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.