# CVE-2026-26145: Microsoft Azure Synapse Elevation of Privilege Vulnerability

> An authorized attacker can elevate privileges in Azure Synapse due to improper access control, requiring a patch to mitigate.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-g6fh-wh88-hxp9

## What is CVE-2026-26145?

CVE-2026-26145 is a medium-severity vulnerability in Microsoft Azure Synapse, published on 2 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper access control in Azure Synapse allows an authorized attacker to elevate privileges over a network.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-26145?

It affects 1 product.


Products: Microsoft Azure Synapse.

## How do I fix CVE-2026-26145?

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

## Is CVE-2026-26145 being exploited?

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

## Other vulnerabilities in Microsoft Azure Synapse

- [CVE-2026-48584](https://insights.sbomify.com/CVE-2026-48584/): Microsoft Azure Synapse Elevation of Privilege Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26145 and fix it if it is affected.

What it is: CVE-2026-26145 is a medium-severity vulnerability in Microsoft Azure Synapse, published on 2 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-26145 in the wild and no public exploit code.

Affected product: Microsoft Azure Synapse. 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-2026-26145/ (Markdown: https://insights.sbomify.com/CVE-2026-26145/index.md)
```

## Sources

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

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