Databricks says it mitigated Java4Shell across all supported Runtime versions.
The flaw allows unauthenticated remote code execution on OpenJDK 17.0.6 and later on x86-64 with AVX-512 VBMI, per Red Hat.
I think restarting customer clusters without asking was the right call.
Databricks said it took that rare step to apply the mitigation fast, before public disclosure of CVE-2026-114938 turned into scanning.
Databricks said it expects no meaningful performance hit from the mitigation.
Serverless customers get patched Runtimes automatically, while classic users must restart to pick them up, the company said. It also said it is contacting custom-image users and has seen no evidence of unauthorized access.
Tenable reports Oracle scores the bug 8.1 and its tests showed code execution without login on Atlassian Jira and Jenkins. That self-hosted exposure makes centralized mitigation look efficient.
The fair objection is that forced restarts interrupt production jobs and punish teams that did nothing wrong.
It survives because silent remote execution beats a failed job every time.
If you run classic clusters, don't wait for a window. Restart now and stay on a supported patched Runtime.





