Skip to main content
Status (November 19, 2026):
  • Patched JDK images: java:21, activemq-artemis:2, kafka:3.6, kafka:3.7, and rust:1 have patched Azul Zulu Java Development Kit (JDK) builds.
  • Mitigated images: java:25, elasticsearch-enterprise:8.19, elasticsearch-enterprise:9.3, kafka:4.1, kafka:4.3, solr:9.1, solr:9.2, solr:9.4, solr:9.6, solr:9.9, solr:10.0, opensearch:2, and opensearch:3 run with the -XX:-UseBASE64Intrinsics mitigation until their JDK vendors ship fixed packages.
  • Legacy Elasticsearch: elasticsearch:7.10 received the mitigation flag as a precaution.
  • Retired images: java:17, java:18, java:19, kafka:3.2, and kafka:3.4 are retired on Upsun Cloud. Upgrade these images instead of waiting for a rebuilt retired image.
  • Redeploy required: Your environment gets the fixed or mitigated image after its next redeploy.
  • No forced redeploys: Upsun Cloud isn’t forcing redeploys for this issue.
  • Still under validation: Composable image OpenJDK packages and non-Java runtime images that bundle Debian OpenJDK still need final status confirmation.
What to do:
  • Your app uses java:21: Redeploy to pick up the patched Zulu 21.0.13.1 image.
  • Your app uses java:25: Redeploy to pick up the mitigation flag, then redeploy again after a fixed Temurin JDK is available.
  • Your app uses java:17, java:18, or java:19: Upgrade to a supported Java version.
  • Your project uses kafka:3.2 or kafka:3.4: Upgrade to a supported Kafka version.
  • Your project uses affected Java-based services: Redeploy so the service containers restart on their fixed or mitigated image.
  • Your project uses composable image OpenJDK or bundled OpenJDK in another runtime: Check the validation notes and plan to redeploy when an updated image is available.
On November 17, 2026, the National Vulnerability Database (NVD) published CVE-2026-114938. The vulnerability is also called Java4Shell by the researchers who disclosed it. It affects OpenJDK’s Base64 decoder on affected JDK builds and hardware. Upsun Cloud has updated images where fixed JDK builds are available and has added the -XX:-UseBASE64Intrinsics mitigation flag where the upstream JDK vendor has not yet shipped a fixed package. Customers get the fixed or mitigated image after a redeploy, and Upsun Cloud isn’t forcing redeploys for this issue.

Update history

  • November 19, 2026, 13:00 UTC: First published.

What was fixed

CVE-2026-114938 affects OpenJDK’s Base64 decoder in affected JDK builds. NVD rates the vulnerability 8.1 (high) on the Common Vulnerability Scoring System (CVSS) v3.1 scale. CVSS rates the severity of vulnerabilities from 0 to 10. The NVD vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, which means the vulnerability is network-reachable, requires high attack complexity, requires no privileges or user interaction, and can affect confidentiality, integrity, and availability.

How the vulnerability works

  • Vulnerable runtime path: According to the Calif technical write-up, malformed Base64 input can trigger a memory-corruption bug in OpenJDK’s optimized x86-64 Base64 decoder. The affected path uses CPU-specific instructions to speed up Base64 processing. On affected JDK builds and hardware, a malformed Base64 tail can write past the end of the decoded buffer. The public write-up describes impact that can include memory disclosure or remote code execution (RCE), depending on how the target application uses Base64 and how exploitation is shaped for that application.
  • Fixed JDK layer: For images where the JDK vendor has shipped a fixed build, Upsun Cloud rebuilt the image with the fixed JDK. Redeploying moves your app or service container onto that image.
  • Mitigation layer: For images where a fixed JDK build isn’t available yet, Upsun Cloud starts the Java Virtual Machine (JVM) with -XX:-UseBASE64Intrinsics. That disables the optimized Base64 intrinsic path described in the vulnerability write-up. You still need to redeploy to pick up the mitigated image, and those images need another update when their JDK vendor ships a fixed package.
This is a runtime issue, not an application framework issue. Updating your Java framework, content management system, or library dependencies doesn’t replace the JDK in your Upsun Cloud image. You need to redeploy onto a fixed or mitigated image, or upgrade to a supported Java version that receives one.

Affected and patched versions

The following table maps confirmed Java application images and Java-based service images to their current Upsun Cloud status:

Check your Java version

If your app uses a java runtime image, check the JDK version in the running app container:
Replace main with your environment name and myapp with your app name. If your project has a single app, you can omit --app. For patched rows, the output should show the patched JDK version from the table above. For mitigated rows, java -version can still show the same JDK version as before the redeploy. List the Java Virtual Machines (JVMs) in the container first:
Find the line for your app’s JVM. Ignore the line that contains JCmd, because that’s the short-lived jcmd process itself. Then check the flags for your app’s main class or JAR:
Replace com.example.Main with the main class or JAR shown by jcmd -l for your app. If more than one line matches your app, use the process ID from the correct jcmd -l line instead. The output should include -XX:-UseBASE64Intrinsics. That confirms the running Java process has the mitigation flag. If the command doesn’t return that flag for your app’s JVM, redeploy and check again. To check the configured app image type, run:
Replace abcdefgh1234567 with your project ID, main with your environment name, and myapp with your app name. The output should show the Java image you configured, such as java:21 or java:25. For managed services, check the service type in your .upsun/config.yaml file and compare it with the table above. Service containers get the fixed or mitigated image when the environment redeploys and the service restarts. Because managed service containers don’t expose a customer shell for jcmd, a successful redeploy after this rollout is the customer-visible check for mitigated service images.

Retired Java versions

Java 17, 18, and 19 are retired on Upsun Cloud. Retired Java runtime images don’t receive rebuilt images for this issue. If your app uses java:17, java:18, or java:19, upgrade to a supported Java version.

What you need to do

Take action if any of the following applies to you:
  • Your app uses java:21 or java:25: Redeploy to pick up the fixed or mitigated image.
  • Your app uses java:17, java:18, or java:19: Upgrade to a supported Java version.
  • Your project uses kafka:3.2 or kafka:3.4: Upgrade to a supported Kafka version.
  • Your project uses affected Java-based services: Redeploy so the service containers restart on their fixed or mitigated images.
  • Your project uses OpenJDK from composable image packages or from a non-Java runtime image: Track the image status and redeploy when the package source is updated.
  • You run Java outside Upsun Cloud: Update your local, container, and continuous integration (CI) JDKs from your JDK vendor.

Redeploy to pick up the fixed or mitigated image

Upsun Cloud applies image updates when your environment redeploys. For CVE-2026-114938, Upsun Cloud isn’t forcing redeploys, so you need to trigger one when you’re ready. If you have a code or configuration change ready, push it through your normal workflow. If you don’t have a code change, force a redeploy:
Replace main with your environment name. After the redeploy finishes, check your Java version.

Upgrade to a supported Java version

Running java:17, java:18, or java:19? Upgrade now. These versions are retired on Upsun Cloud and don’t receive rebuilt images for this issue.
To upgrade, change the type of your app in your configuration file. This example uses Java 21:
Push the change to a preview environment, test it against a copy of your production data, and then merge. After the production redeploy finishes, check your Java version.

Upgrade retired Kafka versions

If your project uses kafka:3.2 or kafka:3.4, upgrade to a supported Kafka version. Retired Kafka service images don’t receive rebuilt images for this issue. Change the service type in your configuration file and test the upgrade in a preview environment:
Kafka upgrades can involve application compatibility and data-retention planning. Test the change with your application before you merge it to production.

Redeploy Java-based services

Java-based services get their fixed or mitigated images when the service container restarts during a redeploy. If your project uses an affected service from the table above, redeploy the environment that contains it:
Replace main with the environment that contains the service. If you run a production service, schedule the redeploy for a time that fits your maintenance process.

If your image is still under validation

Some images still need final status confirmation. This includes composable image OpenJDK packages and non-Java runtime images that bundle Debian OpenJDK 17 or 21. If you depend on one of these images, avoid treating it as patched until its status is confirmed. Where possible, move production Java workloads to java:21 or java:25, or to a Java-based service version listed as fixed or mitigated in the table above. Redeploy when an updated image is available.

If you use OpenJDK in the composable image

The composable image gets OpenJDK from Nix packages that you define in your stack. The rollout notes for this post mark composable image OpenJDK packages as still needing an update. Review your stack.packages and redeploy after the Nix package source for your composable image version has a fixed OpenJDK package. If you need a managed Java runtime instead of a custom package set, use a single-runtime Java image.

Outside Upsun Cloud

Update Java wherever else you run it, including:
  • Local development machines
  • Docker images
  • CI pipelines
  • Build and release workers
Check your JDK vendor for a fixed build. If no fixed build is available for your JDK distribution, use the vendor’s recommended mitigation and update again when a fixed JDK is available.

How Upsun Cloud responded

Upsun Cloud’s response has two parts: fixed JDK builds where vendors have shipped them, and a runtime mitigation where vendors haven’t yet shipped a fixed JDK.

Fixed and mitigated images

Upsun Cloud rebuilt affected images with a fixed JDK where a fixed vendor package was available. For images still waiting on a fixed vendor package, Upsun Cloud added the -XX:-UseBASE64Intrinsics mitigation flag. The affected and patched versions table shows the current status for each image.

Customer action and follow-up

Upsun Cloud isn’t forcing redeploys for this issue, so customers get the fixed or mitigated image after their next redeploy. Images still under validation remain listed separately so you can avoid assuming they’re patched. Retired images are listed separately so you know to upgrade instead of waiting for a rebuilt image. Images that are mitigated rather than patched still need another update when their JDK vendors ship fixed packages.

Questions

If you have questions about your project, contact Upsun Cloud support.
Last modified on November 19, 2026