# CVE-2026-62902: .NET Information Disclosure Vulnerability > An unauthorized attacker can disclose information over a network via untrusted functionality inclusion in the .NET runtime. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 11 Aug 2026 - **Updated:** 28 Oct 2026 - **Also known as:** BELL-CVE-2026-62902, BIT-dotnet-2026-62902, BIT-dotnet-sdk-2026-62902, GHSA-9mrh-pw7c-9mqm, MINI-f2rh-rphp-35jh, MINI-w5g7-5994-25mw, UBUNTU-CVE-2026-62902 ## What is CVE-2026-62902? CVE-2026-62902 is a medium-severity server-side request forgery vulnerability in Microsoft .Net, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Inclusion of functionality from untrusted control sphere in .NET allows an unauthorized attacker to disclose information over a network. Weakness: CWE-918 (Server-Side Request Forgery), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere), CWE-693 (Protection Mechanism Failure) ## Which versions are affected by CVE-2026-62902? 20 open source packages ship an affected version, including Microsoft.WindowsDesktop.App.Runtime.win-arm64, dotnet and dotnet-sdk. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 10.0.0 | 10.0.11 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 10.0.0 | 10.0.11 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 8.0.0 | 8.0.30 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 8.0.0 | 8.0.30 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 9.0.0 | 9.0.19 | | `Microsoft.WindowsDesktop.App.Runtime.win-arm64` | NuGet | From 9.0.0 | 9.0.19 | | `dotnet` | Bitnami | From 8.0.0 | 8.0.30, 9.0.19 | | `dotnet-sdk` | Bitnami | From 8.0.0 | 8.0.30, 9.0.19 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 10.0.0 | 10.0.11 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 10.0.0 | 10.0.11 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 8.0.0 | 8.0.30 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 8.0.0 | 8.0.30 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 9.0.0 | 9.0.19 | | `Microsoft.WindowsDesktop.App.Runtime.win-x64` | NuGet | From 9.0.0 | 9.0.19 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 10.0.0 | 10.0.11 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 10.0.0 | 10.0.11 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 8.0.0 | 8.0.30 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 8.0.0 | 8.0.30 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 9.0.0 | 9.0.19 | | `Microsoft.WindowsDesktop.App.Runtime.win-x86` | NuGet | From 9.0.0 | 9.0.19 | Products: Microsoft .Net, Microsoft Visual Studio 2022, Microsoft Visual Studio 2026. ## How do I fix CVE-2026-62902? Upgrade Microsoft.WindowsDesktop.App.Runtime.win-arm64 to a fixed version for your release line: 10.0.11, 8.0.30 or 9.0.19. ## Is CVE-2026-62902 being exploited? There is no known exploitation of CVE-2026-62902 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-62902 and fix it if it is affected. What it is: CVE-2026-62902 is a medium-severity server-side request forgery vulnerability in Microsoft .Net, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-62902 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.11 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 10.0.0; fixed in 10.0.11 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 8.0.0; fixed in 8.0.30 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 8.0.0; fixed in 8.0.30 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 9.0.0; fixed in 9.0.19 - Microsoft.WindowsDesktop.App.Runtime.win-arm64 (NuGet): affected from 9.0.0; fixed in 9.0.19 - dotnet (Bitnami): affected from 8.0.0; fixed in 8.0.30, 9.0.19 - dotnet-sdk (Bitnami): affected from 8.0.0; fixed in 8.0.30, 9.0.19 - Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): affected from 10.0.0; fixed in 10.0.11 - Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): affected from 10.0.0; fixed in 10.0.11 - Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): affected from 8.0.0; fixed in 8.0.30 - Microsoft.WindowsDesktop.App.Runtime.win-x64 (NuGet): affected from 8.0.0; fixed in 8.0.30 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-62902/ (Markdown: https://insights.sbomify.com/CVE-2026-62902/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62902 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62902 - OSV: https://osv.dev/vulnerability/CVE-2026-62902 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-62902/ Summaries are generated and may contain mistakes; the official description above is the record.