Blog / Java4Shell (CVE-2026-114938): What It Means for Cryptomator and Cryptomator Hub


A critical vulnerability in OpenJDK known as Java4Shell (CVE-2026-114938) has been disclosed, and the German Federal Office for Information Security (BSI) has issued a warning. Since parts of our software are built on Java, we have reviewed all products and our entire infrastructure.

The result in brief:

  • Cryptomator Desktop: We are releasing version 1.19.7 today and highly recommend updating on all devices.
  • Cryptomator for iOS and Android: Not affected.
  • Cryptomator Hub (managed): Not affected. No action is required for the Hub instance.
  • Cryptomator Hub (self-hosted): Hub itself is not affected. The identity provider Keycloak can be affected, depending on the CPU of the server, and should be checked and updated.

We have already informed all Cryptomator Hub customers, managed and self-hosted, by email.

What is Java4Shell?

Java4Shell is a flaw in OpenJDK’s hardware-accelerated Base64 decoder. On x86-64 CPUs that expose the AVX-512 VBMI instruction set, a malformed Base64 value can corrupt the memory of the Java process. Researchers have demonstrated remote code execution without authentication against Keycloak, which decodes such values before authentication.

Is Cryptomator Desktop affected?

The Cryptomator desktop app is built on Java. Based on our current analysis, the risk is lower than for a server such as Keycloak, because the app does not accept requests from the internet and only connects to trusted servers.

Since we cannot rule out that further attack paths will be found, we are releasing Cryptomator 1.19.7 today. It applies the recommended mitigation and disables the JVM’s Base64 intrinsics, the vulnerable code path. The update will be available via the in-app update check and on our downloads page. We highly recommend installing it on all devices.

Are the mobile apps affected?

No. Cryptomator for iOS and Android does not use OpenJDK and is not affected.

Is Cryptomator Hub affected?

No. Hub does not run on a regular Java Virtual Machine but as a native executable built with Mandrel. The Quarkus team has confirmed that such executables are not affected. No Hub update is required.

Hub deployments do, however, include the Java-based identity provider Keycloak. What that means depends on the hosting model.

Are managed Hub instances affected?

No, and they never were. The vulnerable code path is only used on CPUs with AVX-512 VBMI. The servers running our managed instances do not expose this CPU feature, so the flaw could not be triggered at any point.

To be absolutely sure that nothing can be exploited, we have nevertheless built the workaround recommended by the Keycloak team into our Keycloak image and deployed it to all managed instances. Nothing needs to be changed, updated, or restarted on the customer side.

What needs to be done for self-hosted Hub deployments?

In self-hosted deployments, Keycloak can be affected, depending on the CPU of the server it runs on. On an affected system, the flaw can be exploited remotely and without authentication, so the deployment should be checked as soon as possible. We have published the Keycloak image ghcr.io/cryptomator/keycloak:26.8.2.1, which contains the mitigation recommended by Red Hat and the Keycloak team.

1. Check whether the server is affected

Keycloak is only at risk if the CPU of the host (or VM) exposes the AVX-512 VBMI instruction set. This command is run on the machine that executes the Keycloak container (on Kubernetes: on every node that can run it):

grep -m1 '^flags' /proc/cpuinfo \
  | grep -qw avx512vbmi \
  && echo 'AVX-512 VBMI available'

No output means the CPU does not expose AVX-512 VBMI and the deployment is not known to be affected. We still recommend the update below, so the deployment stays protected if it is ever moved to different hardware.

2. Update the Keycloak image

The Keycloak image in the deployment is changed to ghcr.io/cryptomator/keycloak:26.8.2.1, followed by a restart of Keycloak. This image sets -XX:-UseBASE64Intrinsics via JAVA_OPTS_APPEND, which disables the vulnerable code path.

If the image cannot be updated right away, the same mitigation can be applied to the current image by setting the environment variable JAVA_OPTS_APPEND=-XX:-UseBASE64Intrinsics (or adding the flag to an existing value) and restarting Keycloak.

3. Verify the mitigation

After the restart, the flags of the running JVM show whether the mitigation is active:

docker exec <keycloak-container> \
  jcmd io.quarkus.bootstrap.runner.QuarkusEntryPoint \
  VM.flags -all \
  | grep -F UseBASE64Intrinsics

On Kubernetes, kubectl exec <keycloak-pod> -- … is used instead. The mitigation is active if the output contains:

UseBASE64Intrinsics = false

What happens next?

The mitigation fully disables the vulnerable code path, so Cryptomator 1.19.7 and deployments with the updated Keycloak image are protected. The flaw itself is being fixed in OpenJDK. We are monitoring the Keycloak tracking issue and will publish an updated image as soon as a Keycloak release based on a patched OpenJDK build is available. The mitigation stays in place until then.

Where can I find more information?

How can I get help?

If you have any further questions or need assistance during the update, don’t hesitate to contact us at [email protected].