Skip to main content
Platform

Java4Shell vulnerability (CVE-2026-114938) assessment

by Fermín J. Serna

As of November 19 at 10 AM Pacific Time:

Prior to Java4Shell’s public disclosure (CVE-2026-114938), Databricks was already addressing the industry-wide OpenJDK vulnerability.

Databricks is protecting customers in two phases: quick mitigation to disable use of the vulnerable code, and then patching to replace the vulnerable code.

  • Mitigation: We have applied the mitigation to our platform, disabling use of vulnerable code for all supported versions of Databricks Runtime. We do not expect the mitigation to have a meaningful performance impact on customers. In order to apply the mitigation as quickly as possible, we have taken the rare step of proactively restarting affected clusters.
  • Patching: While the mitigation blocks the attack, in an abundance of caution, we will be providing patched versions of supported Databricks Runtimes. Customers on our serverless platform will automatically get them. Customers with classic clusters will need to restart their clusters.

We are also reaching out to customers running custom images.

We have no evidence to indicate any unauthorized access to Databricks products, services, or customers' data.

Get the latest posts in your inbox

Subscribe to our blog and get the latest posts delivered to your inbox.