# CVE-2025-53763: Azure Databricks Elevation of Privilege Vulnerability

> An attacker can elevate privileges in Azure Databricks due to improper access control, requiring a patch to mitigate the risk.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 21 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-pf6v-rv2j-cjh3

## What is CVE-2025-53763?

CVE-2025-53763 is a critical vulnerability in Microsoft Purview Data Governance, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper access control in Azure Databricks allows an unauthorized attacker to elevate privileges over a network.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-53763?

It affects 1 product.


Products: Microsoft Purview Data Governance.

## How do I fix CVE-2025-53763?

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

## Is CVE-2025-53763 being exploited?

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

## Other vulnerabilities in Microsoft Purview Data Governance

- [CVE-2026-57106](https://insights.sbomify.com/CVE-2026-57106/): Data Quality Elevation of Privilege Vulnerability (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53763 and fix it if it is affected.

What it is: CVE-2025-53763 is a critical vulnerability in Microsoft Purview Data Governance, published on 21 Aug 2025. 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-2025-53763 in the wild and no public exploit code.

Affected product: Microsoft Purview Data Governance. 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-2025-53763/ (Markdown: https://insights.sbomify.com/CVE-2025-53763/index.md)
```

## Sources

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

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