dbcve.org
Azure DatabricksApplication · Microsoft

CVE-2026-33107

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in Azure Databricks that allows an unauthorized attacker to elevate privileges over a network. The attacker can potentially make the application perform requests to internal resources, bypassing authentication and authorization controls to escalate privileges.

MitigationApply Azure Databricks security updates when available, implement network segmentation and firewall rules to restrict outbound connections from Databricks resources, and validate that internal service endpoints are not exposed to the Databricks service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure DatabricksApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Azure Databricks workspace URL and public accessibility
    In Azure Portal, go to your Databricks resource and note the workspace URL. Check if the workspace is deployed with 'Public IP' enabled or if it has a public endpoint exposed to the internet via Azure networking configuration or Web Application Firewall settings.
    Affected if The Databricks workspace has a public endpoint accessible from the internet without VPN or private link restrictions.
  2. Review outbound network security rules
    Examine Network Security Groups (NSGs) attached to the Databricks VNet, Azure Firewall rules, or any virtual network appliance configurations that govern outbound traffic from the Databricks workspace subnets.
    Affected if Outbound traffic from Databricks is allowed to arbitrary internet addresses or internal cloud metadata endpoints without strict allowlisting.
  3. Verify metadata service endpoint accessibility
    From within a Databricks cluster or notebook, attempt a test connection to the Azure instance metadata service at http://169.254.169.254/ or check NSG rules for any 'allow' rules targeting this IP address.
    Affected if The Databricks compute resources can reach the cloud metadata endpoint at 169.254.169.254, allowing potential retrieval of instance credentials or service principal tokens.
  4. Check if the Databricks workspace requires authentication for API access
    Attempt to send an HTTP request to the Databricks workspace API endpoint (such as /api/2.0/ or /api/2.1/) without providing valid authentication tokens or bearer credentials, observing whether the request is accepted or rejected.
    Affected if The workspace API accepts unauthenticated requests and returns valid responses rather than 401/403 authentication errors.

You are affected if your Azure Databricks workspace is internet-accessible and accepts unauthenticated API requests, especially if outbound network rules permit arbitrary HTTP requests from Databricks resources to internal metadata endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Azure Databricks security updates when available, implement network segmentation and firewall rules to restrict outbound connections from Databricks resources, and validate that internal service endpoints are not exposed to the Databricks service.

Fix this in Azure Databricks Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33107 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data