Last updated date: 19th November 2026
Advisory publication date: 19th November 2026
Summary
This advisory discloses one high severity vulnerability – CVE-2026-114938 (also known as Java4Shell) – which is an RCE (Remote Code Execution) vulnerability in OpenJDK. The vulnerability affects CloverDX Server and Designer running on unpatched version of Eclipse Temurin JDK 17 or 21 (see Am I affected? section below for more details).
To address the vulnerability, update your Temurin to a fixed version. While no CloverDX updates are required, we recommend you run latest version of CloverDX (7.6.2 at the time of writing). If you cannot upgrade, you can mitigate the issue with a single JVM option (see Mitigation section).
Am I affected?
The vulnerability lies in OpenJDK code and not in CloverDX. To verify if you are affected, check the OpenJDK version by running java -version for Java that runs your Server or Designer. In Server, you can also get JVM version in System info > JVM > JVM implementation version.
You are affected if:
- you run Eclipse Temurin JDK 17 before 17.0.21.1+2 – used by CloverDX 6.2.0 or newer
- you run Eclipse Temurin JDK 21 before 21.0.13.1+2 – used by CloverDX 7.2.0 or newer
Older versions of CloverDX also supported other vendors of OpenJDK. If you use one, check with your JDK vendor to see if you are affected.
What you need to do
CloverDX Server
To address the vulnerability on your CloverDX Server instances, upgrade your Eclipse Temurin JDK to the fixed version. CloverDX Server itself does not require an update, although we strongly recommend you use the latest version available (7.6.2 at the time of writing).
If you are using Java 17, upgrade to Eclipse Temurin 17.0.21.1+2 or newer; if you are using Java 21, upgrade to Eclipse Temurin 21.0.13.1+2 or newer.
How to best approach this depends on the way you deployed your CloverDX Server:
- Your Server runs in Docker or Kubernetes: upgrade your image with the fixed version of CloverDX image appropriate for your version of CloverDX. If you built your image manually based on our dockerfile on GitHub, rebuild the image with fixed Temurin base image.
- Azure Marketplace or AWS Marketplace: upgrade to the latest version of CloverDX once the fix becomes available. If you cannot upgrade, update Java to the appropriate fixed version on your compute node.
- Manual installation (WAR file in your app server): update your Eclipse Temurin JDK using your operating system’s method. Restart the application server after the upgrade.
- CloverDX Server Bundle: bundle is meant for testing and evaluation use only. Install the fixed version of CloverDX bundle once it is available.
CloverDX Designer
Install the fixed version of the Designer as it becomes available. It must be the same version as your CloverDX Server.
If you cannot upgrade, point Designer to the fixed version of Eclipse Temurin JDK that you install on your machine. Use JDK 21 for CloverDX 7.4.0 or newer; JDK 17 for CloverDX 6.3.0 to 7.3.1.
The setting must be changed in two places:
- In CloverDXDesigner.ini – this applies to the Designer itself
- In Window > Preferences > CloverDX > CloverDX Runtime with Alternate JRE configured to use the same JDK as the Designer.
Mitigation
Use this approach if you cannot upgrade. The vulnerability lies in the optimized code that uses special CPU instructions for faster Base64 encoding and decoding on certain CPUs. Disabling this hardware acceleration prevents exploitation of this vulnerability without any negative impact on CloverDX.
To disable hardware acceleration, add -XX:-UseBASE64Intrinsics to your JVM options. This must be configured for both Core and Worker JVMs:
- Core process: update your setenv to include the above parameter to ensure that it is read when your Tomcat starts.
- Worker process: Configure in CloverDX Server Console via Configuration > Setup > Worker > JVM arguments. Alternatively, configure the worker.jvmOptions property in CloverDX configuration file.
The same approach applies to CloverDX Designer:
- Add the parameter on its own line in CloverDXDesigner.ini for the Designer process itself.
- Add the parameter in Window > Preferences > CloverDX > CloverDX Runtime > VM parameters to configure the Designer Runtime.
Fixed product versions
We are releasing artefacts that bundle fixed Temurin versions:
- CloverDX Docker image on DockerHub (and associated Dockerfile in GitHub)
- CloverDX in AWS Marketplace and Azure Marketplace
- Server bundle installers (for evaluation use)
We will update this advisory as soon as fixed versions of CloverDX become available.
Note that CloverDX versions before 7.3.0 no longer receive security patches. You can still fix them by updating Temurin as described above.
Support
If you did not receive this email directly and you want to receive Security Advisory emails like this in the future, subscribe to the CloverDX Security Alerts mailing list.
If you have any questions or concerns regarding this advisory, please raise a CloverCARE support request via Customer Portal.
References
CVE-2026-114938: Java4Shell in OpenJDK
This vulnerability was originally reported only on Oracle Java. However, it affects other builds of OpenJDK – including Eclipse Temurin builds that CloverDX uses.
Original text of the vulnerability disclosure for Oracle:
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Compiler). Supported versions that are affected are Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; Oracle GraalVM for JDK: 17.0.21.0.3 and 21.0.13.0.3; Oracle GraalVM Enterprise Edition: 21.3.20.0.3. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition.
Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service.
- CVE details: CVE-2026-114938 (NVD)
- Severity: HIGH
- CVSS 3.1 score: 8.1
- CVSS 3.1 vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Additional materials
- Calif.io: Java4Shell: Write once, RCE everywhere; available at https://calif.io/java4shell
- Roche Zhang: Java4Shell CVE-2026-114938: Java 17 RCE Checks and Hunting; 18th November 2026; available at https://threatdefence.com/article/java4shell-cve-2026-114938-openjdk-rce-patching-hunting
- Sooraj Shah: Java4Shell: pre-auth RCE flaw in Java 17, 21, 25 and 27, with affected versions and fix (CVE-2026-114938); 17th November 2026; available at https://www.aikido.dev/blog/java-17-rce-vulnerability-cve-2026-114938
- Adoptium: Eclipse Temurin guidance for CVE-2026-114938 "java4shell"; 18th November 2026; available at https://adoptium.net/news/2026/11/temurin-november-2026-cspu-java4shell
- OpenJDK: OpenJDK Vulnerability Advisory: 2026/11/17; 17th November 2026; available at https://openjdk.org/groups/vulnerability/advisories/2026-11-17
- CloverDX Security policy
- CloverDX Support policy
Update history
- 2026-11-19 – This advisory was first published.
Comments 0