# CVE-2024-26203: Azure Data Studio Elevation of Privilege Vulnerability

> Attackers can exploit this vulnerability in Azure Data Studio to elevate privileges on the local system.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Mar 2024
- **Updated:** 3 May 2025
- **Also known as:** GHSA-gj95-32p3-vhr8

## What is CVE-2024-26203?

CVE-2024-26203 is a high-severity vulnerability in Microsoft Azure Data Studio, published on 12 Mar 2024. 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

Azure Data Studio Elevation of Privilege Vulnerability

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-26203?

It affects 1 product.


Products: Microsoft Azure Data Studio.

## How do I fix CVE-2024-26203?

No fix has been published for CVE-2024-26203 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-26203 being exploited?

There is no known exploitation of CVE-2024-26203 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26203 and fix it if it is affected.

What it is: CVE-2024-26203 is a high-severity vulnerability in Microsoft Azure Data Studio, published on 12 Mar 2024. 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-2024-26203 in the wild and no public exploit code.

Affected product: Microsoft Azure Data Studio. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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