# CVE-2023-36049: .NET, .NET Framework, and Visual Studio Elevation of Privilege Vulnerability

> An attacker can exploit this vulnerability in .NET and Visual Studio to elevate privileges on the affected system.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Nov 2023
- **Updated:** 9 Oct 2025
- **Also known as:** BIT-dotnet-2023-36049, BIT-dotnet-sdk-2023-36049, CLEANSTART-2025-FE50155, GHSA-c3hf-8vgx-72rh, UBUNTU-CVE-2023-36049

## What is CVE-2023-36049?

CVE-2023-36049 is a high-severity vulnerability in Microsoft .Net, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

.NET, .NET Framework, and Visual Studio Elevation of Privilege Vulnerability

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-36049?

8 open source packages ship an affected version, including System.Net.Requests, dotnet and dotnet-sdk. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `System.Net.Requests` | NuGet | From 6.0.0 | 6.0.25 |
| `System.Net.Requests` | NuGet | From 6.0.0 | 6.0.25 |
| `System.Net.Requests` | NuGet | From 7.0.0 | 7.0.14 |
| `System.Net.Requests` | NuGet | From 7.0.0 | 7.0.14 |
| `System.Net.Requests` | NuGet | From 8.0.0-rc.2.23480.2 | 8.0.0 |
| `System.Net.Requests` | NuGet | From 8.0.0-rc.2.23480.2 | 8.0.0 |
| `dotnet` | Bitnami | From 6.0.0 | 6.0.25, 7.0.14 |
| `dotnet-sdk` | Bitnami | From 6.0.0 | 6.0.25, 7.0.14 |

Products: Microsoft .Net, Microsoft .Net Framework, Microsoft Visual Studio 2022.

## How do I fix CVE-2023-36049?

Upgrade System.Net.Requests to a fixed version for your release line: 6.0.25, 7.0.14 or 8.0.0.

## Is CVE-2023-36049 being exploited?

There is no known exploitation of CVE-2023-36049 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-2023-36049 and fix it if it is affected.

What it is: CVE-2023-36049 is a high-severity vulnerability in Microsoft .Net, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-36049 in the wild and no public exploit code.

Affected packages and fixed versions:
- System.Net.Requests (NuGet): affected from 6.0.0; fixed in 6.0.25
- System.Net.Requests (NuGet): affected from 6.0.0; fixed in 6.0.25
- System.Net.Requests (NuGet): affected from 7.0.0; fixed in 7.0.14
- System.Net.Requests (NuGet): affected from 7.0.0; fixed in 7.0.14
- System.Net.Requests (NuGet): affected from 8.0.0-rc.2.23480.2; fixed in 8.0.0
- System.Net.Requests (NuGet): affected from 8.0.0-rc.2.23480.2; fixed in 8.0.0
- dotnet (Bitnami): affected from 6.0.0; fixed in 6.0.25, 7.0.14
- dotnet-sdk (Bitnami): affected from 6.0.0; fixed in 6.0.25, 7.0.14

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-2023-36049/ (Markdown: https://insights.sbomify.com/CVE-2023-36049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-36049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-36049
- OSV: https://osv.dev/vulnerability/CVE-2023-36049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-36049/
Summaries are generated and may contain mistakes; the official description above is the record.