Drag the artwork to explore. Use the arrow keys when it is focused.

Security & ExploitsJava Edition

Java4Shell: The Java Bug Every Minecraft Server Owner Should Patch Now (CVE-2026-114938)

A critical bug in Java itself, nicknamed Java4Shell, can crash or in some cases take over Java programs on certain modern Intel and AMD processors. Every Java Minecraft server runs on Java, and the fix shipped on November 17. Here is what server owners and players should do now.

4 min read

TL;DR: CVE-2026-114938 (“Java4Shell”) is a heap overflow in the HotSpot JVM’s fast Base64 decoder. It affects Java 17 (from 17.0.6), 21, 25 and 27 on x86-64 CPUs with AVX-512 VBMI, which includes AMD Zen 4 and newer and Intel Xeon from Ice Lake on. Oracle and OpenJDK fixed it on November 17. A malformed Base64 string can crash the JVM easily; remote code execution has only been shown in lab conditions, and no attacks have been seen yet. No Minecraft-specific exploit has been published. Update Java on your server now.

  • 9.2CVSS 4.0 score from the finder (OpenJDK: 8.1)
  • 17–27Affected Java lines
  • Nov 17Fix released
  • 0Attacks seen in the wild so far

What happened

On November 17, researchers at Calif disclosed a memory-corruption bug in OpenJDK, and Oracle and the OpenJDK Vulnerability Group shipped fixes the same day. To decode Base64 faster, Java uses hand-written code for AVX-512 processors, and that code can write past the end of its buffer when it gets a malformed string. Security firms report that crashing an affected JVM is trivial and repeatable, while turning it into code execution is hard and depends on the CPU. Tenable reports that Calif’s testing showed code execution without a login against apps like Jira and Jenkins. Warnings spread among Minecraft server admins on X within hours.

Is your Minecraft server affected?

Two things must both be true:

  • Your Java version is unpatched 17.0.6 or newer. Paper needs Java 21 for 1.20 to 1.21.11 and Java 25 for 26.1 and newer, so almost every modern server is on an affected line.
  • Your CPU supports AVX-512 VBMI. That covers AMD Zen 4 and newer (EPYC 9004 and later, and the Ryzen 7000 and 9000 chips many game hosts use) and Intel Xeon from Ice Lake through Granite Rapids. ARM servers are not affected.

On Linux, grep -o avx512vbmi /proc/cpuinfo | head -1 prints avx512vbmi if your CPU has it. On a shared host you may not be able to check, so ask your provider or just update.

What it means for Minecraft

Nobody has shown an attack through Minecraft itself yet, and we are not claiming one exists. The realistic risk is anything on your server that decodes Base64 sent by strangers: plugins that read player-supplied textures or data, web panels and stores, and other Java services on the same machine. Even without code execution, a crash is a cheap way to knock a server offline.

Players are a separate question. The Minecraft Launcher ships its own Java runtime, and Mojang has not said whether or when that runtime will be updated. We will update this story when it does.

Update, November 19: what launchers are doing

ATLauncher now says the bug affects both vanilla and modded Minecraft clients and servers on AVX-512 CPUs, which include some newer AMD desktop chips. It updated its launcher to add the mitigation flag automatically when you use the Java it provides. With the official Minecraft Launcher, Prism or MultiMC you can add -XX:-UseBASE64Intrinsics yourself under the installation’s JVM arguments; a community guide on GitHub walks through each launcher. ATLauncher warns that the flag makes Java 8 crash, so only use it on Java 17 and newer (Minecraft 1.18 and later).

What you should do now

  • Update Java to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, or your vendor’s matching build (Temurin, Microsoft OpenJDK, or your Linux distro’s package once it lands). Check with java -version and restart the server.
  • Can’t update today? Calif suggests adding -XX:-UseBASE64Intrinsics to your start flags, which turns the fast path off. This flag is not in Oracle’s or OpenJDK’s advisories, so treat it as a stopgap and test it first.
  • Hosted server? Ask your host which Java build your node runs. Many panels let you pick a Java image; choose an updated one.
  • Update your other Java apps on the same box too, such as proxies, panels and bots.

For more server security stories, see our server security hub.

Sources 6

Did you enjoy this story?