TL;DR: We have analyzed CVE-2026-114938 (“Java4Shell”) and believe the risk for RSKj node operators is low. No urgent action is required. Out of an abundance of caution, we are preparing RSKj 9.0.5, a release that fully closes the vulnerable code path. Operators who want extra protection today can follow the optional steps in Part 2.
Part 1: The situation
What is Java4Shell?
CVE-2026-114938, nicknamed “Java4Shell”, is a memory corruption vulnerability in the Base64 decoder of OpenJDK, disclosed on November 17, 2026. It affects Java 17 (from 17.0.6), 21, 25 and 27, and every distribution built on them, including Eclipse Temurin, Amazon Corretto and Ubuntu’s OpenJDK packages.
The flaw is in a hardware-accelerated version of the decoder. It only runs on x86-64 servers whose CPUs support the AVX-512 VBMI instruction set, such as recent Intel Xeon (Ice Lake, Sapphire Rapids) and AMD EPYC (Genoa, Turin) processors. Servers on ARM64 (for example AWS Graviton or Ampere) and older x86-64 CPUs are not affected.
Our assessment: low risk for RSKj nodes
To be exploited, an attacker has to get the node’s Java runtime to decode a specially crafted Base64 input. Our team analyzed how RSKj interacts with the affected component:
- We found no use of Java’s Base64 decoder in RSKj or the libraries it ships with. The node’s P2P network uses binary RLP encoding, and its JSON-RPC and WebSocket interfaces use hexadecimal encoding (0x…). None of the node’s inbound interfaces showed a path to the flaw.
- Java itself uses the decoder when it reads a server’s certificate during an outbound HTTPS connection: a server can send its certificate as Base64 text, and Java decodes it. By default, RSKj makes one such connection when it starts, to look up its public IP address if none is configured. An attacker who controls that server or can intercept the node’s network traffic could make the node decode their input, but that alone is not enough to exploit the flaw.
Exploitation also requires the affected hardware described above, and security researchers agree that turning this flaw into remote code execution is difficult even where it can be reached. As of November 19, 2026, there are no reports of it being exploited in the wild.
What we are doing
Out of an abundance of caution, we are preparing RSKj 9.0.5, a release that fully closes the vulnerable code path, regardless of your hardware or Java version. We will announce it on our usual channels as soon as it is available.
Until then, no urgent action is required. If you want extra protection now, Part 2 explains how to check whether your server could be affected and how to protect it in a few minutes.
Part 2: How to protect your node (optional)
The steps in this part are optional. They are for operators who want to act before RSKj 9.0.5 is available.
Step 1: Check whether your server could be affected
Run this on the server that hosts the node:
grep -m1 ‘^flags’ /proc/cpuinfo | tr ‘ ‘ ‘\n’ | grep -E ‘^(avx512f|avx512bw|avx512vbmi|bmi2)$’
This lists which of the CPU features used by the vulnerable code are present. If the output includes all four flags (avx512f, avx512bw, avx512vbmi and bmi2), your CPU can run the vulnerable code. If avx512vbmi is missing, your node is not affected and you do not need to do anything else. If your node runs on ARM64, it is not affected either.
Cloud virtual machines can expose different CPU flags depending on the instance type, so run the check on each instance type you use.
Step 2: Choose your protection
There are two ways to protect your node:
- Update Java (permanent fix). Install Java 17.0.21.1 or later. If you run the JAR with your own Java installation, get it from your Java provider, for example Eclipse Temurin. Ubuntu PPA users get it through apt (see below).
- Turn off the affected code path (temporary). Add the Java option -XX:-UseBASE64Intrinsics to the node’s startup command. This disables the hardware-accelerated Base64 decoder and has no noticeable effect on node performance. It is the fastest option for Docker users, because the official RSKj image already bundles its own Java.
Pick the instructions below that match how you run the node.
Docker (docker run)
Before you start: check that your database is on a volume. Changing the Java option means replacing the container, and docker rm deletes any data stored inside the container itself. Data on a named volume or a mounted host folder is kept.
To see where your container stores its data, run:
docker inspect <container-name> –format ‘{{range .Mounts}}{{.Type}} {{.Name}} {{.Source}} -> {{.Destination}}{{println}}{{end}}’
The node’s data directory must appear in the output. Then reuse that same volume or folder when you start the node again, with the same -v option you used before. If the output is empty, your database lives inside the container and would be deleted: mount a volume first, or expect the node to sync again from scratch. If the volume has a long random name, it was created automatically; pass that name explicitly with -v <volume-name>:<path>, or Docker will create a new, empty one.
Important: DEFAULT_JVM_OPTS replaces the default value -Xms4G. Always keep -Xms4G and any memory options you already use, and add the new option at the end.
1. Stop and remove the container. Keep your data volume; do not remove it.
docker stop <container-name>
docker rm <container-name>
2. Start the node with your usual docker run command, adding this option before the image name:
docker run -d –name <container-name> \
-e DEFAULT_JVM_OPTS=”-Xms4G -XX:-UseBASE64Intrinsics” \
<your other options> rsksmart/rskj:<your tag> <your node options>
3. Run the checks in Check the node below.
Docker Compose
1. In docker-compose.yml, add this line under environment: for the RSKj service (keep -Xms4G and your other memory options):
environment:
– DEFAULT_JVM_OPTS=-Xms4G -XX:-UseBASE64Intrinsics
2. Recreate the container:
docker compose up -d
3. Run the checks in Check the node below.
Do not use docker compose down -v: it deletes the node’s volumes, including the database.
JAR (no Docker)
1. Stop the node.
2. Add -XX:-UseBASE64Intrinsics to your java command and start the node:
java -Xms4G -XX:-UseBASE64Intrinsics -cp <PATH-TO-THE-RSKJ-JAR> co.rsk.Start
3. Run the checks in Check the node below.
Alternatively, update your Java installation to 17.0.21.1 or later and restart the node. In that case you do not need the option.
Ubuntu PPA
The rskj package runs the node with Ubuntu’s OpenJDK 17 (openjdk-17-jre). Ubuntu published the fixed Java in USN-9155-1 and delivers it through regular updates.
1. Update Java:
sudo apt update
sudo apt install –only-upgrade openjdk-17-jre openjdk-17-jre-headless
2. Restart the node so that it loads the updated Java:
sudo systemctl restart rsk
3. Check the Java version that the node uses. Find the Java path in the ExecStart line, then run that path with -version. The output must show 17.0.21.1 or later.
systemctl cat rsk | grep ExecStart
<java-path-from-ExecStart> -version
4. Run check 2 (block number) in Check the node below. Check 1 does not apply, because this fix does not use a Java option.
Check the node
Check 1 (Docker and JAR only): the option is active. The output must contain -XX:-UseBASE64Intrinsics.
Docker:
docker exec <container-name> sh -c ‘for p in /proc/[0-9]*; do tr “\0″ ” ” < $p/cmdline 2>/dev/null; echo; done’ | grep — -XX:-UseBASE64Intrinsics
JAR:
ps -ef | grep [c]o.rsk.Start
Check 2: the node syncs. Run this command twice, one minute apart. The block number must increase.
curl -s -X POST -H “Content-Type: application/json” \
–data ‘{“jsonrpc”:”2.0″,”method”:”eth_blockNumber”,”params”:[],”id”:1}’ \
http://localhost:4444
If your node’s JSON-RPC port is not 4444, or your container does not publish it, adjust the address.
Remove the option later
When you update to Java 17.0.21.1 or later, or to RSKj 9.0.5, remove -XX:-UseBASE64Intrinsics and restart the node.
Do you have further questions?
Please contact us through our Rootstock Discord Server for technical questions and support. You can also reach out with any feedback you would like to share with us through our social media channels and forums.
Website | Twitter | Developer Portal | Discord | Youtube | Blog

