CVE-2026-96234: 
C# Analyse et atténuation des vulnérabilités

CVE-2026-96234 is an Origin Validation Error (CWE-346) in Microsoft .NET and Visual Studio that allows an unauthenticated network attacker to disclose sensitive information, with user interaction required to trigger the vulnerability. The flaw resides in the Microsoft.WindowsDesktop.App.Runtime (WPF) package and affects .NET 8.0 (< 8.0.32), .NET 9.0 (< 9.0.21), .NET 10.0 (< 10.0.13), .NET 11.0 (< 11.0.0-rc.2), Microsoft Visual Studio 2022 version 17.14 (< 17.14.42), and Microsoft Visual Studio 2026 version 18.10 (< 18.10.4). It was disclosed and patched on October 13, 2026, as part of Microsoft's October 2026 Patch Tuesday. The CVSS v3.1 base score is 5.3 (Moderate) (Microsoft MSRC, GitHub Advisory).

The vulnerability is classified as CWE-346 (Origin Validation Error), meaning the affected .NET WPF runtime does not properly verify the source or origin of data or communications. According to the GitHub advisory, the fix includes restrictive XAML and XPS security changes: blocking unsafe URI fetching and navigation, propagating untrusted-input state through hyperlink navigation, adding TrueType font protection and XAML nesting-depth limits, and avoiding caching of positive DNS zone-policy decisions. Exploitation requires network access and user interaction (e.g., a user opening or interacting with a malicious WPF application or document), and no privileges are required on the attacker's side. The attack complexity is rated High, indicating specific conditions must be met for successful exploitation (GitHub Advisory, Microsoft MSRC).

Successful exploitation results in a high confidentiality impact — an unauthorized attacker can read sensitive information from the affected system over the network. There is no integrity or availability impact. The vulnerability is limited in scope to the affected component (Scope: Unchanged), reducing the risk of lateral movement, but the potential exposure of sensitive data processed by WPF applications (e.g., credentials, tokens, or application data) remains a meaningful risk for Windows-based .NET deployments (GitHub Advisory, Microsoft MSRC).

As of the disclosure date, there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation (Microsoft MSRC). The EPSS score is 0.0, reflecting a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The NVD SSVC assessment also classifies exploitation as "none" and the attack as non-automatable, further reducing near-term risk.

Microsoft has released patched versions addressing this vulnerability. Users should upgrade to the following versions immediately:

• .NET 8.0: Update to 8.0.32 or later
• .NET 9.0: Update to 9.0.21 or later
• .NET 10.0: Update to 10.0.13 or later
• .NET 11.0: Update to 11.0.0-rc.2 or later
• Visual Studio 2022 (17.14): Update to 17.14.42 or later
• Visual Studio 2026 (18.10): Update to 18.10.4 or later

Visual Studio users will be prompted to update automatically, which also updates bundled .NET SDKs. Developers who have deployed self-contained applications targeting affected versions must recompile and redeploy those applications. After updating, restart all affected applications for changes to take effect (GitHub Advisory, Microsoft MSRC).

The vulnerability was noted as part of Microsoft's October 2026 Patch Tuesday, which addressed 1,411 flaws and 3 zero-days according to BleepingComputer coverage. Zero Day Initiative (ZDI) included it in their October 2026 security update review. No significant independent researcher commentary or community controversy has been observed for this specific CVE, consistent with its moderate severity and lack of active exploitation.