Summary
Liquibase's VEX file lists CVE-2026-114938 (Java4Shell) as exploitable, but practical exposure for Liquibase is low. A fix is planned for the Java that comes with Liquibase, and a workaround is available today for both bundled and external Java. To use the VEX file in your scanner, see VEX files in Liquibase Secure.
Applies to: Liquibase Secure images and Windows installers (bundled Temurin 21), and Liquibase running on your own Java.
Is Liquibase exposed?
Liquibase is a short-lived command-line process that accepts no inbound connections, and only x86-64 CPUs with AVX-512 VBMI are affected. The main remaining risk is a run that connects to a database or service an attacker controls or impersonates. The VEX entry for this CVE documents this analysis.
Applications that embed the Liquibase libraries run on their own Java runtime and are affected through that runtime.
Java bundled with Liquibase
Liquibase Secure images and Windows installers ship Temurin 21, and no Temurin release with the fix is available yet. Once one is, Liquibase will release a Liquibase Secure version that bundles Temurin 21.0.13.1 or later. There isn't a release date or version to share yet.
Liquibase is fix-forward, so the fix will be in the latest version.
Running Liquibase on your own Java
If you run Liquibase on your own Java, the upgrade is handled by your Java Runtime vendor. Update to a Java Runtime that includes the November 17, 2026, OpenJDK security fixes: 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 or later. The OpenJDK advisory has the details.
Workaround until you can upgrade
Start Liquibase with -XX:-UseBASE64Intrinsics to turn off the vulnerable hardware-accelerated decoder:
- Set
JAVA_OPTSto-XX:-UseBASE64Intrinsicsbefore running theliquibaseorliquibase.batlauncher. - For Docker, pass
-e JAVA_OPTS=-XX:-UseBASE64Intrinsicstodocker run. - For an application that embeds Liquibase, add the flag to that application's JVM options.
Need Help?
If you have questions after applying the workaround or upgrading, contact Liquibase Support and include your Liquibase version, how you run Liquibase (Docker image, Windows installer, ZIP or TAR, or embedded), and your Java version.
Comments
0 comments
Article is closed for comments.