WSA-2026-001: Java4Shell (CVE-2026-114938) in the bundled Java runtime
| Advisory | WSA-2026-001 |
|---|---|
| Version | 1, interim. This advisory will be updated when the situation changes. |
| Status | Workaround available |
| Severity | High: CVSS 3.1 base score 8.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HSource: Oracle as CVE Numbering Authority; the OpenJDK advisory and the NVD state the same score |
| CVE | CVE-2026-114938 |
| Component | OpenJDK (Eclipse Temurin) |
| Published | 2026-11-20 |
| webPDF version | Status | Remediation or reason |
|---|---|---|
| 10.0 to 10.0.7 | Affected | No fix available yet; workaround available (see Remediation) |
| 9.0, all releases | Not affected | The vulnerable code is not included |
| 8.0, all releases | Not affected | The vulnerable code is not included |
Summary
CVE-2026-114938, also known as "Java4Shell", is a vulnerability in the Java runtime (OpenJDK) that the OpenJDK project published on November 17, 2026. It affects an optimized routine for Base64 decoding that the Java runtime uses only on processors with the AVX-512 VBMI instruction set extension. On such processors, decoding specially crafted Base64 data can write past the end of a memory buffer. The vulnerability has a CVSS 3.1 base score of 8.1 (High).
webPDF ships with its own Java runtime. Every release of webPDF 10.0 up to and including 10.0.7 contains an affected version. A webPDF release with a corrected Java runtime is not available yet. Until then, a Java option switches off the affected routine, see Workaround.
Affected and not affected versions
| webPDF version | Bundled Java runtime | Affected |
|---|---|---|
| 10.0 to 10.0.7 | OpenJDK 21.0.6 to 21.0.13 | Yes |
| 9.0, all releases | OpenJDK 11 | No |
| 8.0, all releases | OpenJDK 11 | No |
This applies to every installation type: the Windows setup, the Linux packages, and the Docker image. The Java 11 runtime of webPDF 9.0 and 8.0 does not contain the affected decoding routine, and the OpenJDK advisory does not list Java 11 for this vulnerability.
The Java runtime of each webPDF release is named in the "List of used components" of its changelog entry, for example for webPDF 10.0.7.
Conditions for exploitation
All of the following must apply:
- The server has an x86-64 processor with the AVX-512 VBMI extension, for example Intel Xeon processors from the Ice Lake generation on or AMD processors from the Zen 4 generation on.
- The Java runtime decodes Base64 data that an attacker controls and that ends with padding characters (
=), using the standard or the URL-safe decoder of the Java class library (java.util.Base64). The MIME decoder is not affected. - The just-in-time compiler of the Java runtime has compiled the decoding routine, which happens after it has run many times.
We do not publish details on how such data could reach webPDF. If a server meets the processor condition, assume that it is affected.
Check your installation
The bundled Java runtime shows whether the processor has AVX-512 VBMI. Run the command on the machine where webPDF runs:
-
Windows (command prompt or PowerShell, in the installation folder of webPDF):
.\jre\bin\java.exe -Xlog:os+cpu -version 2>&1 | findstr avx512_vbmi -
Linux:
/opt/webpdf/jre/bin/java -Xlog:os+cpu -version 2>&1 | grep avx512_vbmi -
Docker (replace
webpdfwith the name of your container):docker exec webpdf /opt/webpdf/jre/bin/java -Xlog:os+cpu -version 2>&1 | grep avx512_vbmi
If the command prints a line, the processor has AVX-512 VBMI. If it prints nothing, the processor does not have it, and the vulnerability cannot be exploited on this machine.
In a virtual machine or a container, the result shows the processor features that the host passes on. Repeat the check when the server can move to other hardware, for example in a virtualization cluster.
Remediation
Fix
A webPDF release with a corrected Java runtime is not available yet. This advisory will be updated when it is.
Workaround
The Java option -XX:-UseBASE64Intrinsics switches off the optimized Base64 routines of the Java runtime, including
the affected one.
- It slows down only the Base64 processing of the Java class library, not the server as a whole.
- It does no harm on servers without AVX-512 VBMI.
- It does not replace the update to a corrected Java runtime.
Some sources also name -XX:UseAVX=2. That option switches off further processor optimizations and costs more
performance; for this vulnerability, -XX:-UseBASE64Intrinsics is sufficient.
Whether you apply the workaround is your decision: only you know how webPDF is deployed, connected and protected in your environment. Where webPDF reads its Java options is described in Java environment. The following sections describe where to set the option for each installation type.
Workaround on Windows
webPDF 10.0.7:
- Open
C:\ProgramData\webPDF\conf\webPDF.service.vmoptionsif webPDF runs as a Windows service, otherwiseC:\ProgramData\webPDF\conf\webPDF.vmoptions. - Add
-XX:-UseBASE64Intrinsicsas a new line at the end of the file. - Restart webPDF (the Windows service or the application).
An update keeps this file.
webPDF 10.0 to 10.0.6: These versions read the Java options only from the files in the installation folder.
- Open
webPDF.service.vmoptions(Windows service) orwebPDF.vmoptionsin the installation folder of webPDF. - Add
-XX:-UseBASE64Intrinsicsas a new line at the end of the file. - Restart webPDF (the Windows service or the application).
Every update replaces these files and removes the option. After an update to webPDF 10.0.7, enter the option in the
file in C:\ProgramData\webPDF\conf instead, as described above.
Workaround on Linux
The Linux packages start webPDF with systemd and take the Java options from the environment setting JAVA_PARAMETERS.
-
Open a drop-in for the service:
sudo systemctl edit webpdf -
Add the option to
JAVA_PARAMETERS:override.conf[Service]Environment="JAVA_PARAMETERS=-Xmx4g -Xms1g -XX:-UseBASE64Intrinsics"JAVA_PARAMETERSreplaces the default-Xmx4g -Xms1gas a whole. If you already setJAVA_PARAMETERS, add the option to your value and keep your memory settings. -
Restart the service:
sudo systemctl restart webpdf
An update does not change the drop-in. If webPDF is started with SysVinit (/etc/init.d/webpdf), add the option to
javaOpt in /opt/webpdf/webpdf.sh instead; every update replaces that file.
Workaround with Docker
Add the option to the environment setting JAVA_PARAMETERS of the container, then recreate the container, for example
with docker compose up -d:
services:
webPDF:
environment:
- JAVA_PARAMETERS=-Xmx4g -Xms1g -XX:-UseBASE64Intrinsics
With docker run, pass it as -e JAVA_PARAMETERS="-Xmx4g -Xms1g -XX:-UseBASE64Intrinsics"; in Kubernetes, set the
same value in the env section of the container. JAVA_PARAMETERS replaces the default -Xmx4g -Xms1g as a whole,
so keep your memory settings in it.
Verify the workaround
The tool jcmd of the bundled Java runtime shows the options of the running server. It reaches only Java processes
that run under the same user account.
-
List the Java processes. webPDF is the process with
webPDF.starter.jar:# Linuxsudo -u webpdf /opt/webpdf/jre/bin/jcmd -l# Dockerdocker exec webpdf /opt/webpdf/jre/bin/jcmd -l -
Show its options, with the process number from step 1:
# Linuxsudo -u webpdf /opt/webpdf/jre/bin/jcmd <process number> VM.flags# Dockerdocker exec webpdf /opt/webpdf/jre/bin/jcmd <process number> VM.flags
The workaround is active if the output contains -XX:-UseBASE64Intrinsics.
On Windows, .\jre\bin\jcmd.exe in the installation folder works the same way when it runs under the account that
webPDF runs under. If that is not possible, for example for the Windows service, make sure that the option is in the
file and that webPDF was restarted after the change.
References
- OpenJDK Vulnerability Advisory of November 17, 2026
- CVE-2026-114938 in the CVE List
- CVE-2026-114938 in the National Vulnerability Database
- Java environment: where webPDF reads its Java options
- Security updates: how webPDF delivers security updates
Contact
For questions about this advisory, contact support@softvision.de. To report a vulnerability in webPDF, write to security@softvision.de; see our vulnerability disclosure policy.
Revision history
| Version | Date | Change |
|---|---|---|
| 1 | 2026-11-20 | Initial publication. |