Information about the Java vulnerability CVE-2026-114938 (“Java4Shell”)
On 17 November 2026, a vulnerability in the Java runtime OpenJDK was published: CVE-2026-114938, also known as “Java4Shell”. It is not a vulnerability in PDFreactor itself, but it affects the Java runtime that is packaged with PDFreactor, as well as other Java runtimes PDFreactor may run on.
Who is affected
Only computers with an x86-64 CPU that supports AVX-512 VBMI are affected, for example Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen Zen 4 or newer. ARM64 is not affected. On Linux, you can check the CPU with this command. If all four flags are listed, the CPU meets this condition.
grep -o -w -E 'avx512f|avx512bw|avx512vbmi|bmi2' /proc/cpuinfo | sort -uAffected Java versions are Java 17.0.6 to 17.0.21, Java 21 before 21.0.13.1, Java 25 before 25.0.5.1 and Java 27 before 27.0.1.1. This includes the Java runtime packaged with the PDFreactor 12 Docker images, with the installers of PDFreactor 12.0.0 to 12.7.3 that include Java (except the updated 12.7.3 installers, see below) and with the installers of PDFreactor 11.6.9 to 11.6.12 that include Java.
In PDFreactor, the affected Java function is used, among others, for input documents sent to the Web Service and for the JavaScript function atob() in documents. JavaScript is enabled by default since PDFreactor 12.
PDFreactor update
The PDFreactor 12.7.3 installers that include Java have been updated with Eclipse Temurin 21.0.13.1, which fixes the vulnerability. The version number remains 12.7.3, so to get the fix, install the updated installer, also if you already have 12.7.3. An updated Docker image will follow, and we will update this page when it is available.
If you run PDFreactor on your own Java installation, for example with the PDFreactor Java library, check its version against the list above and update Java if needed.
Workaround
If you use the Docker image or cannot update right away, you can apply the following workaround at your own discretion. Adoptium, the provider of Eclipse Temurin, names the Java option -XX:-UseBASE64Intrinsics as an interim mitigation. It disables the hardware-accelerated Base64 code in Java, so Base64 processing can become slower.
- Docker image: set the environment variable
JAVA_OPTIONSto-XX:-UseBASE64Intrinsics(append it ifJAVA_OPTIONSis already set) and recreate the container, for exampledocker run -e JAVA_OPTIONS="-XX:-UseBASE64Intrinsics" ... - Installed Web Service: add the option on its own line at the end of
jetty-base-pdfreactor/start.d/main.ini(PDFreactor 11:jetty/start.d/main.ini) in the installation directory, for example/opt/PDFreactoron Linux, and restart the PDFreactor service - Java library: add the option to the Java command line of your application and restart it
The alternative option -XX:UseAVX=2 mentioned in some reports prevents Java from starting on ARM64.
More information
If you have questions, please contact us at support@realobjects.com.

