Security alerts · November 18, 2026

Java4Shell: OpenJDK and Oracle Java flaw can allow code execution without login on some servers

On November 17, 2026, Oracle and the OpenJDK project fixed a Base64 decoder flaw that, on servers with newer Intel and AMD chips, can crash Java or let an attacker run code without logging in. No exploitation has been confirmed yet. Patch internet-facing apps first.

What happened

On November 17, 2026, Oracle and the OpenJDK project released fixes for CVE-2026-114938. The researchers at Calif who found it named it “Java4Shell”. The flaw is in OpenJDK, which Calif calls the most popular Java runtime. Its code underpins Oracle Java and builds from many other vendors, such as Amazon Corretto, Eclipse Temurin and Azul Zulu.

The problem sits in the code that decodes Base64 data. Base64 is a common way to write binary data as text. It shows up in logins, tokens, cookies and file uploads. On some processors Java uses a faster version of the decoder, and that is where the bug is.

Calif’s researchers say they were able to run their own code without logging in on default installations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. According to The Hacker News, other security labs have so far reproduced crashes and a memory leak, but not code execution.

Real-world exploitation has not been confirmed. The flaw is not in the CISA KEV catalog, the EU vulnerability database EUVD lists no exploitation, and Canada’s Cyber Centre is not aware of attacks. Even so, the US agency CISA has urged organizations to patch immediately.

Why it is dangerous

This is an out-of-bounds write, also called a heap overflow. Picture a form with a ten-character field where someone types twelve characters and the last two spill into the next field. With malformed input, the decoder writes dozens of bytes past the end of its reserved memory and damages neighboring data. Java does reject the input in the end, but only after the write has happened.

The most common result is a Java crash, meaning the service goes down. According to Calif, careful preparation can also let an attacker read sensitive memory, much like the well-known Heartbleed bug, or run their own code. There is no universal exploit, and each application needs a different approach.

The attacker needs no login and attacks over the network. Servers often decode Base64 before checking whether a user is logged in, for example in HTTP Basic headers, JWT tokens or SAML messages. Calif also describes the reverse direction: a Java program that connects over TLS to a malicious server can be compromised too. Oracle’s description says a successful attack can result in takeover of Java, with high impact on confidentiality, integrity and availability.

The CVSS score (0 to 10) expresses severity. Oracle rates the flaw 8.1 under CVSS 3.1, noting it is hard to exploit but needs no login. Red Hat gives a preliminary 9.8 (CVSS 3.0), Amazon 8.8, and Calif 9.2 under CVSS 4.0. The CISA KEV catalog lists flaws with confirmed exploitation, and this one is not in it yet.

Who is affected

The flaw only affects systems where all three conditions listed by CERT-EU are met:

  • Java runs on an x86-64 CPU with AVX-512 VBMI: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, or AMD EPYC and Ryzen Zen 4 and newer.
  • The faster Base64 decoder is active, which is the default on such CPUs.
  • Attacker-controlled data reaches the decoder, for example login headers, tokens, cookies or TLS data.

Affected versions are Oracle Java SE and OpenJDK 17 from 17.0.6 to 17.0.21, the 21, 25 and 27 lines at 21.0.13, 25.0.5, 27.0.1 and earlier, Java SE 8 Performance Pack 8u511b33-perf, GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and GraalVM Enterprise Edition 21.3.20.0.3. Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, BellSoft Liberica, SAP SapMachine and Red Hat build of OpenJDK are affected as well.

Typical targets are company servers running Jira, Confluence, Jenkins, Keycloak or Artifactory, as well as in-house apps built on Spring Boot or Apache Struts. ARM64 servers, CPUs without AVX-512 VBMI and standard Java 8 and 11 are not affected. Note that the same container image can be vulnerable on one server and not on another.

How to check if you are affected

All commands below only read information and change nothing. First, on Linux, check whether the CPU has the required instructions. All four flags must appear in the output, otherwise the server is not affected:

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

On Windows, find the CPU model in Task Manager and compare it with the list above. Then check the Java version. Apps like Jira or Confluence often ship their own bundled Java, so confirm which one the running processes actually use. The last command shows the path to a given process’s Java, which you can then run with -version:

java -version
ps -eo pid,args | grep '[j]ava'
sudo readlink /proc/<PID>/exe

In containers, run java -version inside the container. Many applications also show the Java version in their admin area under system information. The last command shows whether the faster decoder is enabled by default on this server. If a running app shows -XX:-UseBASE64Intrinsics in the ps output, the decoder is turned off for it.

docker exec <container> java -version
java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep UseBASE64Intrinsics

How to fix it

Fixed Oracle and OpenJDK builds were released on November 17, 2026:

  • Java 17: 17.0.21.1, Java 21: 21.0.13.1, Java 25: 25.0.5.1, Java 27: 27.0.1.1
  • Java 8 Performance Pack: 8u513
  • GraalVM for JDK 17.0.21.1 and 21.0.13.1, GraalVM Enterprise Edition 21.3.20.1
  • Amazon Corretto: 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4
  • Azul Zulu (free builds): 17.70.201, 21.54.201, 25.38.201 and 27.30.201

Red Hat has not yet released fixes for RHEL 8, 9 and 10 or for its OpenJDK 17, 21 and 25 builds. According to The Hacker News, Eclipse Temurin, Microsoft Build of OpenJDK and BellSoft Liberica had not listed fixed builds as of November 18, 2026. SAP released SapMachine 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 without stating what they fix.

  • Inventory every Java installation, including those bundled in applications, container images and appliances (CISA’s advice).
  • Start with internet-facing systems, as CERT-EU recommends.
  • Install the fixed Java build, and for apps with bundled Java, the update from the app’s vendor.
  • Restart all Java processes, and rebuild and redeploy container images.

If you cannot update right away, CERT-EU lists the option below, which turns off the faster decoder. The alternative is -XX:UseAVX=2, which disables AVX-512 entirely and can reduce performance. Use it only on x86-64, because Java on ARM will not start with it. Both options need a restart, and you should remove them after updating.

-XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics

CISA also advises validating and restricting Base64 input at the application boundary, enforcing input-size limits and limiting unauthenticated access. According to The Hacker News, a reverse proxy that waits for complete requests, as nginx does by default, blocks some attacks but not all.

What if you may already be compromised

The Hacker News lists the following signs that may point to attack attempts. None of them proves a compromise, and their absence does not mean the server is safe:

  • Base64 tokens of 32 characters or more that end in = and whose length is not a multiple of 4, especially in Authorization headers.
  • Bursts of IllegalArgumentException errors from java.util.Base64$Decoder in application logs.
  • Unexplained hs_err_pid Java crash logs.

By default, Java writes hs_err_pid files to the process’s working directory. The first command below finds those from the last 30 days. The second counts Base64 decoder errors in application logs, including compressed ones. Adjust the log path for your application.

sudo find / -xdev -name 'hs_err_pid*.log' -mtime -30 -ls 2>/dev/null
sudo zgrep -c 'java.util.Base64\$Decoder' /path/to/logs/*.log*

Also look for unknown user accounts in the application, new files in its directories and unusual outbound connections from the server. If you find anything suspicious, bring in an incident response specialist. Change passwords and keys stored on the server and consider restoring from a trusted backup.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.