● Critical · CVSS 10

How to Fix CVE-2026-33107: Azure Databricks Elevation of Privilege in Azure Databricks

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-33095: Use-after-free in Microsoft Office — Use-after-free in Microsoft Office
How to Fix CVE-2026-26154: Improper input validation in Microsoft Windows Server — Improper input validation in Microsoft Windows Server
How to Fix CVE-2026-21528: Critical Vulnerability in Azure IoT Explorer , Critical Vulnerability in Azure IoT Explorer
How to Fix CVE-2026-40363: Path Traversal in Microsoft 365 Apps for Enterprise , Path Traversal in Microsoft 365 Apps for Enterprise
How to Fix CVE-2026-26134: Microsoft Office Elevation of Privilege in Microsoft Office for Android , Microsoft Office Elevation of Privilege in Microsoft Office for Android

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

⚡ At a glance


Severity	CVSS 10, Critical
Actively exploited?	No
Affected	Microsoft Azure Databricks (-)
Fixed in	See vendor advisory
Type (CWE)	CWE-918: CWE-918: Server-Side Request Forgery (SSRF)

CVE-2026-33107 is a azure databricks elevation of privilege in Microsoft Azure Databricks. The fix is to upgrade to see vendor advisory and apply the runnable commands below.

What is CVE-2026-33107?

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

In practical terms, a successful attacker gets server-side request forgery against internal resources. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You are affected if you run Microsoft Azure Databricks at a version listed in the Affected row above. Probe your installed build with the commands below.


[System.Environment]::OSVersion.Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

How to fix CVE-2026-33107

The primary fix is to upgrade to the patched build listed in the Fixed in row above (See vendor advisory). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33107
sudo apt-get update
sudo apt-get install --only-upgrade azure-databricks
# Confirm the installed version meets or exceeds <patched-version>
dpkg -s azure-databricks | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security azure-databricks -y
rpm -q azure-databricks

Windows (PowerShell, admin)


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33107
winget upgrade --id 'Microsoft.AzureDatabricks' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\AzureDatabricks-<patched-version>.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows): detect, back up, upgrade, verify, log


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33107
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\AzureDatabricks-Patch-CVE-2026-33107.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-33107 remediation for Microsoft Azure Databricks"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Azure*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'<patched-version>') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\AzureDatabricks-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Microsoft\Azure Databricks"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer
$installer = "$env:TEMP\AzureDatabricks-<patched-version>.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Azure*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'<patched-version>') {
    Write-Log "SUCCESS: now at $verify (>= <patched-version>)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux): detect, back up, upgrade, verify, log


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33107
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/azure-databricks-patch-cve-2026-33107.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-33107 remediation for Microsoft Azure Databricks"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s azure-databricks >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' azure-databricks)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q azure-databricks >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' azure-databricks)
    PKG_MGR=dnf
else
    log "azure-databricks not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: azure-databricks=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/azure-databricks-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/azure-databricks /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y azure-databricks
else
    sudo dnf upgrade --security -y azure-databricks
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' azure-databricks)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' azure-databricks)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against <patched-version> and restart the affected service if needed."

If you cannot patch immediately

These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.

No official vendor workaround is published for this CVE; patching is the documented fix. The runnable hardening below is generic defense in depth, not a substitute for the patch.

Restrict the affected service to trusted networks (Linux):


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33107
sudo iptables -A INPUT -p tcp --dport <port> -s 10.0.0.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport <port> -j DROP

Windows Firewall equivalent:


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33107
New-NetFirewallRule -DisplayName 'Allow affected service from admin subnet' -Direction Inbound -Action Allow -Protocol TCP -LocalPort <port> -RemoteAddress 10.0.0.0/24
New-NetFirewallRule -DisplayName 'Block affected service from everywhere else' -Direction Inbound -Action Block -Protocol TCP -LocalPort <port>

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected output: the KB ID listed in the vendor advisory appears with an InstalledOn date that matches your patch window.

Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-33107 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-33107 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-33107?

CVSS rates it 10 (Critical). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take Azure Databricks offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-33107 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

Official vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33107
NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-33107
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor advisory before applying changes in production.*