Link Search Menu Expand Document

CVE-2026-114938 (Java4Shell)

OpenJDK Base64 Decoder Vulnerability

Last Updated: 19th November 2026


   
Severity Critical (CVSS 4.0: 9.2 / Oracle CVSS 3.1: 8.1)
Status Action required
Affected products EzSign, Certdog (when running on an affected Java version)


Summary

CVE-2026-114938, known as “Java4Shell”, is a memory corruption flaw in the optimised Base64 decoder of the OpenJDK HotSpot JVM. Under certain conditions an unauthenticated remote attacker who can send Base64 data to an application may be able to crash it or execute code

The vulnerability is in the Java runtime, not in Krestfield code. Any Krestfield product running on an affected Java version should be updated to use a patched Java runtime


A system is only exposed when all of the following are true:

  • It runs an affected Java version (Java 17.0.6 or later on the 17 line, or Java 18 to 27, before the fixed builds listed below)
  • It runs on an x86-64 CPU with AVX-512 VBMI support (e.g. Intel Xeon Ice Lake or newer, AMD Zen 4 or newer). ARM64 is not affected
  • Attacker controlled data reaches Java’s Base64 decoder

Even if you are unsure whether your hardware is affected, we recommend that you update


Affected Java Versions

Java version Affected?
Java 8 (standard builds) Not affected
Java 8 Oracle Enterprise Performance Pack (8u511-perf) Affected
Java 11 Not affected
Java 17 (17.0.6 and later) Affected until patched
Java 18 - 20, 22 - 24, 26 (end of life) Affected, no fix planned. Upgrade to a supported release
Java 21, 25, 27 Affected until patched


Patched Java Builds

Install the patched build from the same vendor you currently use:

Vendor Java 17 Java 21 Java 25 Java 27
Oracle JDK 17.0.21.1 21.0.13.1 25.0.5.1 27.0.1.1
Amazon Corretto 17.0.21.1.2 21.0.13.1.2 25.0.5.1.2 27.0.1.1.4
Azul Zulu 17.0.21.1+2 21.0.13.1+2 25.0.5.1+2 27.0.1.1+4
Oracle GraalVM 17.0.21.1 21.0.13.1 n/a n/a
Microsoft Build of OpenJDK Not yet available Not yet available Not yet available n/a
Red Hat build of OpenJDK Not yet available Not yet available Not yet available n/a

If your vendor has not yet released a fix, apply one of the Temporary Mitigations below, or switch to a vendor that has


What Should We Do

EzSign

EzSign runs on the Java runtime configured in the envs.bat (Windows) or envs.sh (Linux/Unix) file, located here:

[EzSign Install]\EzSignServer\bin

If you are running EzSign under Java 8 or Java 11 you are not affected and no action is required (unless you are using Oracle’s Java 8 Enterprise Performance Pack)


STEP 1 - Identify the Java version in use

Open envs.bat (or envs.sh) in the [EzSign Install]\EzSignServer\bin folder

On Windows, the Java location is set by the JAVA_HOME parameter e.g.

set JAVA_HOME=%EZSIGN_HOME%\java\jdk-26.0.1

On Linux/Unix, the Java location is set by the JAVA parameter e.g.

export JAVA=/opt/java/java/jdk1.8.0_341

If you are using the Krestfield EzSign Service (Windows), the Java location is instead set in EzSign Service Config under Java Location. See the EzSign Service Guide


Confirm the version by running java -version from that location e.g.

[Java Location]\bin\java -version

If this reports Java 8 or Java 11 then no further action is required


STEP 2 - Download a patched Java runtime

Download a patched build from the Patched Java Builds table above and install or extract it to a location of your choice e.g.

C:\Program Files\Java\jdk-25.0.5.1


STEP 3 - Stop EzSign

Stop the EzSign server using the ezsign-daemon-stop.bat (or ezsign-daemon-stop.sh) script

If you are using the EzSign Service, open the services snapin and stop Krestfield EzSign Service


STEP 4 - Update the Java location

Edit envs.bat and update JAVA_HOME to point to the new Java installation folder e.g.

set JAVA_HOME=C:\Program Files\Java\jdk-25.0.5.1

On Linux/Unix, edit envs.sh and update JAVA e.g.

export JAVA=/opt/java/jdk-25.0.5.1

Save the file

If you are using the EzSign Service, open EzSign Service Config and update the Java Location for each Server, then click Apply


STEP 5 - Start EzSign

Start the EzSign server using the ezsign-daemon-start.bat (or ezsign-daemon-start.sh) script, or start the Krestfield EzSign Service

Note that a running Java process will continue to use the old runtime until it is restarted


STEP 6 - Confirm

Check the EzSign logs to confirm the server has started and run java -version from the new Java location to confirm the patched version is in use


Certdog

Certdog is supplied with a bundled Java runtime. A script is provided that will update this to the latest, patched Java runtime

The script will:

  • Download the latest, patched Java runtime
  • Stop the Certdog service
  • Backup the existing Java runtime
  • Apply the latest, patched Java runtime
  • Start the Certdog service


STEP 1 - Download the script

Download the Java upgrade script from here


STEP 2 - Unblock the zip file

Once the file has been downloaded, right click the file and choose Properties. Tick the Unblock option at the bottom of the dialog (if present) and click OK. See Unblock for more details


STEP 3 - Unzip the script

Unzip the file and save the contents to:

[certdog install]\install


STEP 4 - Run the script

Open a PowerShell prompt, navigate to the [certdog install]\install folder and run:

.\upgrade-java.ps1

Once the script completes, the Certdog service will be running on the patched Java runtime


Temporary Mitigations

If you are unable to update Java immediately, start the JVM with one of the following options. These are not a replacement for patching

  • -XX:-UseBASE64Intrinsics
    • Works on all platforms. Disables the vulnerable optimisation. Applications that decode a lot of Base64 data may run slightly slower
  • -XX:UseAVX=2
    • x86-64 only. Do not use on ARM64 as the JVM will fail to start


The option can be set using the JAVA_TOOL_OPTIONS environment variable e.g. on Windows add the following System Environment Variable:

JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics

Restart the EzSign or Certdog services


Checking Whether Your CPU is Affected (Linux)

Run the following. The host is only affected if all four flags are printed:

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


Other Krestfield Products

Product Status
CRL OCSP Monitor Not affected
Signature Toolkit Not affected


References


Revision History

Date Change
19th November 2026 Initial advisory


More Information

Contact Krestfield Support for more information