On November 17, 2026, security firms disclosed a critical vulnerability in OpenJDK, tracked as CVE-2026-114938 and informally dubbed "Java4Shell." The bug lies in a Base64 decoder and affects Java 17, 21, 25 and 27 running on processors with AVX-512 VBMI instruction support, and that's exactly the kind of hardware that powers a huge chunk of Minecraft servers today, including popular Paper and Spigot based setups.

How the Base64 decoder bug works

The vulnerability works like this: a specially crafted Base64 string triggers invalid memory writes in the optimized decoder implementation used by the JVM on x86-64 processors with AVX-512 VBMI, including newer AMD Ryzen 7000 and 9000 chips and Google Cloud C3 instances. In practice, this lets an unauthenticated attacker corrupt Java's heap memory, read sensitive data, and in the worst case execute arbitrary code on the server without ever logging in.

Oracle rated the flaw at 8.1 on the CVSS 3.1 scale, while Calif, the firm that reported the bug, gave it as high as 9.2 on the newer CVSS 4.0 scale. As researchers cited by TechTarget point out, the flaw was found in just an hour using an AI model scanning the decoder's code. The US agency CISA has called on system administrators to deploy patches immediately.

Where the name Java4Shell comes from

The name isn't random, it immediately calls to mind Log4Shell from December 2021, one of the most notorious vulnerabilities in Java's history. That bug, found in the Log4j library and rated the maximum 10.0 on the CVSS scale at the time, hit the Minecraft world in a spectacular way: all it took was pasting a specially crafted message into a server's chat to remotely execute code on it. Java4Shell works differently on a technical level, but raises similar concerns, since it also affects a fundamental, widely used feature of the Java runtime rather than a single application or third-party library.

Minecraft servers in the danger zone

For players running their own Java Edition servers, what matters most is which Java version their server software requires. Paper on the latest game releases runs on Java 25, the standard server software for versions 1.20 through 1.21.11 runs on Java 21, and older releases from 1.17 to 1.19 require Java 17. Every one of these branches is affected by the vulnerability if the machine running the server has a processor with AVX-512 VBMI.

This isn't an exotic scenario. Many server owners listed on, say, the Minecraft servers list use dedicated machines or VPS instances based on new Ryzen chips, which is now the standard offering from most hosting companies. If you're renting a machine to run a Minecraft server, it's worth asking your provider what processor is underneath and whether the Java runtime has already been updated.

Mojang hasn't patched its own launcher yet

The issue also affects the game's own launcher. The Java runtimes bundled with the official launcher are still versions 21.0.7 and 17.0.15, which do not include the fix. Until Mojang ships an update, the only temporary safeguard for regular players is adding the JVM argument -XX:-UseBASE64Intrinsics in the launcher settings, which disables the vulnerable code path. You can check the current game releases and installers on the Minecraft Java Edition download page.

What server administrators should do

For anyone running their own server, the list of actions is simple and worth going through as soon as possible:

  • Update Java to the patched releases: 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, depending on the branch you're using.
  • Restart the server so the new Java version actually takes effect, since downloading the patch alone doesn't change anything without a process restart.
  • If the server is rented, ask your hosting provider when the Java runtime on their infrastructure will be updated.
  • If self-hosting, temporarily apply the flag -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 if a full update isn't possible yet.

Detailed, technical step-by-step instructions for various systems and panels, including Pterodactyl and Docker configurations, have been compiled by ComputingForGeeks in a guide specifically addressing Minecraft servers. It's a good starting point for less experienced administrators before turning to their own guides for configuration.

Bedrock and Realms out of the attack's reach

Good news for Bedrock Edition players: according to an analysis by OneLiteFeather, the vulnerability does not affect Bedrock Edition or Minecraft Realms, since those environments are managed directly by Mojang and don't expose the vulnerable Base64 decoding path in a way an external attacker could reach.

Sophos notes that, so far, no confirmed cases of Java4Shell being exploited in the wild have been recorded. Still, given that the bug allows attacks without any login and Minecraft is one of the most popular platforms with publicly accessible servers in the world, administrators shouldn't wait for the first incident before updating.

Sources