Overview
Java4Shell is the name given to CVE-2026-114938, a vulnerability in the Java runtime published on November 17, 2026. Several CAST Highlight components run on Java and are affected only under specific hardware conditions. This bulletin explains how to check whether your deployment is affected, a configuration change that protects it today, and what CAST is doing to deliver a fix.
| Severity | Status | Published | Last updated |
|---|---|---|---|
| High | Affected – mitigation available, fix pending the fixed Java runtimes | 2026-11-18 | 2026-11-18 |
In short
- Your deployment is affected only if it runs on a recent x86-64 processor with the AVX-512 VBMI instruction set (Intel Xeon 3rd generation or later, AMD EPYC 4th generation or later). Arm processors and older processors are not affected. A one-line check is provided below.
- CAST Highlight SaaS platforms: no action is required from customers. CAST handles the hosted platforms.
- On-premise deployments and the scan agent: if they are affected, a configuration change protects them now, without upgrading CAST Highlight.
- CAST will publish a CAST Highlight release with fixed Java runtimes as soon as they are available. This bulletin will be updated when it is available.
- At the time of writing, CAST is not aware of any exploitation of this vulnerability against CAST Highlight.
What is Java4Shell?
Java4Shell is a memory corruption flaw in an optimized Base64 decoder of OpenJDK. This decoder is used only on x86-64 processors that support AVX-512 VBMI. Exploiting it can crash the application or run code on the server. Any Java application running on such a processor can be affected, not only CAST software.
- Affected: Java 17.0.6 and later Java 17 releases, Java 21 and Java 25.
- Not affected: Java 8 and Java 11.
- Fixed releases started on November 17, 2026: Oracle and OpenJDK 17.0.21.1, 21.0.13.1 and 25.0.5.1, Amazon Corretto and Azul Zulu. Eclipse Temurin had not published its fix at the time of writing.
Is my deployment affected?
| Deployment | Affected | Action |
|---|---|---|
| CAST Highlight SaaS (hosted by CAST) | Handled by CAST | None for customers |
| On-premise Docker: Highlight Portal, Keycloak | Depends on the processor | Steps 1 and 2, then mitigation |
| On-premise Docker: CVE DB service | Depends on the processor | Steps 1 and 2, then mitigation |
| Highlight scan agent (CLI) on Windows | Depends on the processor and the Java version | Steps 1 and 2, then mitigation |
| Highlight scan agent (CLI) Docker image | Depends on the processor of the Docker host | Step 1, then mitigation |
Step 1 – Check the processor
Run this command on each Docker host, and on each Linux machine running the scan agent:
$ grep -c avx512vbmi /proc/cpuinfo
0: the machine is not affected. No action is required.- Any other number: the machine is affected. Continue with Step 2.
- On Windows, check the processor model in Task Manager > Performance > CPU and compare it with the list below.
Processors supporting AVX-512 VBMI: Intel Xeon Scalable 3rd generation (Ice Lake) and later, including Xeon 6 Performance-cores (not Efficient-cores); AMD EPYC 4th generation (Genoa, Bergamo) and later.
| Cloud provider | Affected | Not affected |
|---|---|---|
| AWS | Intel 6th generation and later: m6i, c6i, r6i and variants, i4i, x2idn, x2iedn, m7i, m7i-flex, c7i, r7i, r7iz, i7ie, m8i, c8i, r8i, i7i. AMD 7th generation and later: m7a, c7a, r7a, hpc7a, m8a, c8a, r8a | Intel 5th generation and earlier: m5, c5, r5, t3, m5zn, z1d. AMD 6th generation and earlier: m5a, m6a, c6a, r6a, t3a. All Graviton (Arm) |
| Azure | Intel v5/v6: Dsv5, Ddsv5, Esv5, Edsv5, Ebsv5, Dlsv5, Bsv2, Dsv6, Ddsv6, Esv6, Edsv6, Dlsv6. AMD v6 and later: Dasv6, Dadsv6, Easv6, Falsv6, Fasv6, HBv4, HX, Dasv7 | Intel v3/v4: Dv3, Dsv3, Dv4, Dsv4, Ev4, Fsv2. AMD v4/v5: Dav4, Dasv5, Easv5, Basv2. Arm: Dpsv5, Dpsv6, Bpsv2 |
| Google Cloud | C3, C3D, C4, C4D, N4, N4D, M3, Z3, H3, and N2 when running on Intel Ice Lake | N1, E2, N2D, T2D, C2, C2D, M1, M2, Arm (T2A, C4A, N4A) |
The command above gives the definitive answer for each machine.
Step 2 – Check which components you use
| Component | Java runtime affected |
|---|---|
| Highlight Portal | Depends on its Java version (check below) |
| Keycloak (SSO) | Yes – Java 21 |
| CVE DB service | Depends on its Java version (check below) |
| Highlight scan agent (CLI) | Depends on the Java installed on the machine |
Highlight scan agent Docker image (based on eclipse-temurin:25-jre-alpine) |
Yes – Java 25 |
| PostgreSQL, Nginx | No – no Java runtime |
An affected Java runtime is affected only on a machine where Step 1 does not return 0. On any other machine, no component is affected, whatever its Java version.
To check the Java version used by a container:
$ sudo docker ps --format '{{.Names}} {{.Image}}'
$ sudo docker exec <container> java -version
For the scan agent, run java -version with the same user and the same PATH or JAVA_HOME as the agent.
Users only need to reach the HTTPS port of the portal. Keycloak administration, CVE DB and database ports should not be reachable from user networks. This reduces exposure but does not replace the mitigation.
What do I need to do?
If the check returns 0 on every machine, or if your components run on Java 8 or 11, no action is required. Otherwise:
- Apply the mitigation for your deployment type below. It disables the optimized Base64 decoder with the Java option
-XX:-UseBASE64Intrinsics. No noticeable performance impact is expected, and the option has no effect on machines that are not affected. - Check that only the needed ports are reachable.
- Install the CAST Highlight release with fixed Java runtimes when it is published. The mitigation can stay in place after the update.
Applying the mitigation restarts the services. Do it when no scan or result upload is running.
CAST Highlight SaaS
No action is required. CAST applies the mitigation on the hosted platforms and will deploy the fixed Java runtimes.
Docker on Linux – Portal and Keycloak
Add the settings to the docker-compose.override.yml file next to your docker-compose.yml, so that they are kept when you update CAST Highlight. Add them under the existing service sections, not in a second services: section. If the variable already has a value, add the option at the end, separated by a space.
- Portal service:
JAVA_TOOL_OPTIONS - Keycloak service:
JAVA_OPTS_APPEND(Keycloak reads this variable)
Use the service names of your own docker-compose.yml. Example:
services:
portal:
environment:
JAVA_TOOL_OPTIONS: "-XX:-UseBASE64Intrinsics"
keycloak:
environment:
JAVA_OPTS_APPEND: "-XX:-UseBASE64Intrinsics"
Recreate the containers from the installation folder:
$ sudo docker compose up -d
Check the result:
$ sudo docker logs <portal-container> 2>&1 | grep "Picked up JAVA_TOOL_OPTIONS"
Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics
$ sudo docker top <keycloak-container> | grep -c -- "-XX:-UseBASE64Intrinsics"
1
Docker on Linux – CVE DB service
Apply the same procedure on the machine hosting the CVE DB service. In its docker-compose.override.yml:
services:
cvedb:
environment:
JAVA_TOOL_OPTIONS: "-XX:-UseBASE64Intrinsics"
Then recreate the container and check its logs:
$ sudo docker compose up -d
$ sudo docker logs <cvedb-container> 2>&1 | grep "Picked up JAVA_TOOL_OPTIONS"
Microsoft Windows – Highlight scan agent
- Create the
JDK_JAVA_OPTIONSsystem environment variable with the value-XX:-UseBASE64Intrinsics, in System Properties or from a command prompt run as administrator:setx /M JDK_JAVA_OPTIONS "-XX:-UseBASE64Intrinsics"If the variable already exists, add the option at the end, separated by a space.
- Open a new command prompt. Restart the machine if the agent runs as a scheduled task or a service.
- Check that the output of the next scan contains
NOTE: Picked up JDK_JAVA_OPTIONS: -XX:-UseBASE64Intrinsics.
Use JDK_JAVA_OPTIONS, not JAVA_TOOL_OPTIONS. The variable applies to every Java application on the machine. Java 8 ignores JDK_JAVA_OPTIONS, but refuses to start when the option comes from JAVA_TOOL_OPTIONS, which would break other Java 8 applications on the machine.
Alternatively, update the Java runtime used by the agent to a fixed release, within the Java versions supported by CAST Highlight.
On Linux or macOS, set the same variable in the environment of the user running the agent, for example export JDK_JAVA_OPTIONS="-XX:-UseBASE64Intrinsics".
Docker – Highlight scan agent image
The public Docker image of the scan agent is based on eclipse-temurin:25-jre-alpine and runs Java 25. A container uses the processor of the machine running Docker, so the image is affected only when that machine has a processor with AVX-512 VBMI. The same image is not affected on an older processor or on an Arm machine, where Docker uses the arm64 variant of the image. With Docker Desktop on Windows or on an Intel Mac, the processor of the computer is the one that counts.
To check the processor seen by the container:
$ docker run --rm --entrypoint grep <image-cli> -c avx512vbmi /proc/cpuinfo
If the result is not 0, pass the option when you start the container:
$ docker run -e JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics <image-cli> ...
In a docker-compose.yml file or a CI pipeline, add the same environment variable to the scan agent service or job. The image only contains Java 25, so JAVA_TOOL_OPTIONS can be used safely here. Check that the scan output contains Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics.
The mitigation is no longer needed once you use a scan agent image built on a fixed Java runtime.
If you need help, contact CAST Support or your CAST Highlight Customer Success Manager.
Leave a Reply