Unsafe Deserialization in Microsoft.WindowsDesktop.App.Runtime.win-x64 (CVE-2026-50646)
Summary
Vulnerability in Microsoft.WindowsDesktop.App.Runtime.win-x64 (CVE-2026-50646). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 8.0.29 or later.
Original description
The description as published by the source.
Protection mechanism failure in .NET Framework allows an unauthorized attacker to execute code locally.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50646 has been found in Microsoft.WindowsDesktop.App.Runtime.win-x64.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade Microsoft.WindowsDesktop.App.Runtime.win-x64 to 8.0.29 or later.
If unsure, ask your IT team or search "Microsoft.WindowsDesktop.App.Runtime.win-x64 CVE-2026-50646" on the vendor's site.
CVE-2026-50646 (Microsoft.WindowsDesktop.App.Runtime.win-x64) — CWE-502 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 8.0.29 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in Microsoft.WindowsDesktop.App.Runtime.win-x64.
Check the vendor advisory for the affected versions of Microsoft.WindowsDesktop.App.Runtime.win-x64.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 8.0.29.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Microsoft.WindowsDesktop.App.Runtime.win-x64' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Microsoft.WindowsDesktop.App.Runtime.win-x64' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Microsoft.WindowsDesktop.App.Runtime.win-x64を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Microsoft.WindowsDesktop.App.Runtime.win-x64 to 8.0.29ステージング環境で 8.0.29 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-50646 dotnet7
References
- advisory msrc.microsoft.com
- package github.com
- web github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com