Skip to content
Händle & Korte GmbH · Rathausufer 20 · 40213 Düsseldorf +49 211 6022440 info@hk-net.de Deutsch

Customer notice

Java vulnerability “Java4Shell”

Our systems are not affected – please check your own Java applications on virtual servers.

The German Federal Office for Information Security (BSI) warns of a critical vulnerability in OpenJDK and other Java runtimes. It has the identifier CVE-2026-114938, is known as “Java4Shell” and is rated “critical” with 9.2 out of 10 under CVSS 4.0. Oracle and the OpenJDK maintainers published an advisory on 17 November 2026.

The flaw is in the accelerated Base64 decoding of the Java Virtual Machine: with input containing unexpected padding characters, the size of the output buffer is miscalculated, so adjacent memory can be overwritten. Under certain conditions, attackers can execute code remotely, read memory contents or take applications down (denial of service). According to the BSI, no successful attacks are known so far, but first exploitation attempts have been observed.

Who is affected

Affected are OpenJDK from version 17.0.6 and Java runtimes based on it, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM. A successful attack without authentication has already been demonstrated against Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate.

The vulnerable code is only used on x86-64 processors with AVX-512 VBMI – in servers, for example Intel Xeon from Ice Lake (including Sapphire, Emerald and Granite Rapids) and AMD EPYC and Ryzen from Zen 4. ARM64 processors are not affected. In addition, the application must process Base64 input that an attacker can control, such as credentials (HTTP Basic), SAML data or tokens.

Our systems

Our own systems are not affected. However, the processors of our Windows cloud support AVX-512 VBMI, and this feature is also available inside the virtual servers. If you run your own Java applications there, the vulnerability may affect them – please check them as described below.

What you should do

The BSI recommends identifying and updating systems with Java runtimes as quickly as possible – publicly reachable applications first. For Oracle Java SE, versions 8u513, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 fix the vulnerability; for other Java runtimes and Linux distributions, the updates from the respective vendor apply. Java processes must be restarted after the update. If software or a container ships its own Java, follow the vendor’s instructions.

Until you can update, the vulnerable acceleration can be disabled with one of two JVM startup options: -XX:-UseBASE64Intrinsics or – on x86-64 systems only – -XX:UseAVX=2. Both may affect performance. If neither is possible right away, access to affected applications should be temporarily limited to trusted networks.

This command shows whether a Linux server meets the conditions – it is affected if all four values are returned:

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

On Windows, this command shows whether a Java installation uses the vulnerable acceleration (UseAVX = 3 and UseBASE64Intrinsics = true):

java -XX:+PrintFlagsFinal -version | findstr "UseAVX UseBASE64Intrinsics"

Our support team will be happy to help if you have any questions.

Source: BSI situation report (BITS 306673) of 18 November 2026.

← All news

What can we do for you?

Whether it’s a specific question or a new project – we’re happy to help.