# CVE-2026-33107: Azure Databricks Elevation of Privilege Vulnerability

> An unauthorized attacker can exploit Server-Side Request Forgery in Azure Databricks to elevate privileges over the network.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-xrc8-933j-f74c

## What is CVE-2026-33107?

CVE-2026-33107 is a critical server-side request forgery vulnerability in Microsoft Azure Databricks, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server-side request forgery (ssrf) in Azure Databricks allows an unauthorized attacker to elevate privileges over a network.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Microsoft Azure Databricks.

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

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

## Is CVE-2026-33107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33107 is a critical server-side request forgery vulnerability in Microsoft Azure Databricks, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33107 in the wild and no public exploit code.

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

## Sources

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

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