# CVE-2026-50650: .NET Framework Elevation of Privilege Vulnerability > An attacker can exploit improper code generation in .NET Framework to elevate privileges locally on affected systems. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Jul 2026 - **Updated:** 28 Oct 2026 - **Also known as:** BIT-dotnet-2026-50650, BIT-dotnet-sdk-2026-50650, GHSA-2969-4q4w-w5h3, MINI-32p5-7x6g-4h3q, MINI-xc4j-j93w-cfp4, UBUNTU-CVE-2026-50650 ## What is CVE-2026-50650? CVE-2026-50650 is a high-severity code injection vulnerability in Microsoft .Net, published on 14 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description Improper control of generation of code ('code injection') in .NET Framework allows an unauthorized attacker to elevate privileges locally. Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2026-50650? 20 open source packages ship an affected version, including Microsoft.WindowsDesktop.App.Runtime.win-arm64, dotnet and dotnet-sdk. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 10.0.0 | 10.0.10 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 10.0.0 | 10.0.10 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 8.0.0 | 8.0.29 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 8.0.0 | 8.0.29 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 9.0.0 | 9.0.18 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 9.0.0 | 9.0.18 | | `dotnet` | Bitnami | From 8.0.0 | 8.0.29, 9.0.18 | | `dotnet-sdk` | Bitnami | From 8.0.0 | 8.0.29, 9.0.18 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 10.0.0 | 10.0.10 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 10.0.0 | 10.0.10 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 8.0.0 | 8.0.29 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 8.0.0 | 8.0.29 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 9.0.0 | 9.0.18 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 9.0.0 | 9.0.18 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 10.0.0 | 10.0.10 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 10.0.0 | 10.0.10 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 8.0.0 | 8.0.29 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 8.0.0 | 8.0.29 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 9.0.0 | 9.0.18 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 9.0.0 | 9.0.18 | Products: Microsoft .Net, Microsoft .Net Framework. ## How do I fix CVE-2026-50650? Upgrade Microsoft.WindowsDesktop.App.Runtime.win-arm64 to a fixed version for your release line: 10.0.10, 8.0.29 or 9.0.18. ## Is CVE-2026-50650 being exploited? There is no known exploitation of CVE-2026-50650 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft .Net - [CVE-2024-43498](https://insights.sbomify.com/CVE-2024-43498/): .NET and Visual Studio Remote Code Execution Vulnerability (critical 9.8) - [CVE-2024-0057](https://insights.sbomify.com/CVE-2024-0057/): NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability (critical 9.1) - [CVE-2026-96957](https://insights.sbomify.com/CVE-2026-96957/): .NET Security Feature Bypass Vulnerability (high 8.8) - [CVE-2026-69439](https://insights.sbomify.com/CVE-2026-69439/): .NET and Visual Studio Elevation of Privilege Vulnerability (high 8.8) - [CVE-2026-71328](https://insights.sbomify.com/CVE-2026-71328/): .NET and Visual Studio Remote Code Execution Vulnerability (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-50650 and fix it if it is affected. What it is: CVE-2026-50650 is a high-severity code injection vulnerability in Microsoft .Net, published on 14 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-50650 in the wild and no public exploit code. Affected packages and fixed versions: - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 10.0.0; fixed in 10.0.10 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 10.0.0; fixed in 10.0.10 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 8.0.0; fixed in 8.0.29 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 8.0.0; fixed in 8.0.29 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 9.0.0; fixed in 9.0.18 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 9.0.0; fixed in 9.0.18 - dotnet (Bitnami): affected from 8.0.0; fixed in 8.0.29, 9.0.18 - dotnet-sdk (Bitnami): affected from 8.0.0; fixed in 8.0.29, 9.0.18 - Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): affected from 10.0.0; fixed in 10.0.10 - Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): affected from 10.0.0; fixed in 10.0.10 - Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): affected from 8.0.0; fixed in 8.0.29 - Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): affected from 8.0.0; fixed in 8.0.29 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-50650/ (Markdown: https://insights.sbomify.com/CVE-2026-50650/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50650 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50650 - OSV: https://osv.dev/vulnerability/CVE-2026-50650 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-50650/ Summaries are generated and may contain mistakes; the official description above is the record.