A bug in Java’s Base64 decoder can let attackers run code on servers without logging in. Oracle shipped fixes on November 17.

Key points

  • The vulnerability CVE-2026-114938, nicknamed “Java4Shell,” sits in OpenJDK’s Base64 decoder and was disclosed by Calif.io on November 17, 2026.
  • The researchers score it 9.2 out of 10 under CVSS 4.0 and say OpenJDK 17.0.6 and later is affected, but only on x86-64 processors with AVX-512 VBMI.
  • Oracle released fixed builds on November 17, 2026; as of that day, security firm Upwind reported no exploitation in the wild and no listing in CISA’s Known Exploited Vulnerabilities catalog.
  • If you can’t patch right away, the JVM flag -XX:-UseBASE64Intrinsics turns off the affected code path.

A critical flaw in Java’s Base64 decoder, known as Java4Shell (CVE-2026-114938), can let attackers run code on servers without logging in. It affects Java 17 and later on processors with AVX-512 VBMI, and patches are available.

Advertisement

Any US company or agency that runs Java directly, or uses software with Java bundled in, should treat this as a priority. The products the researchers tested are mostly server applications common in American IT shops, from Jira and Confluence to Jenkins and Keycloak.

What Java4Shell lets attackers do

The bug is in the Base64 decoder Java uses to convert text-encoded data back into bytes. According to the technical analysis by Calif.io, an optimized routine for processors with AVX-512 VBMI miscalculates the length and write mask at the end of the input. That leads to a write outside the intended memory area.

The researchers say a crafted input of 64 characters followed by “=” is enough to trigger it. From there, they demonstrate memory leaks and remote code execution. Their own score is 9.2 under CVSS 4.0, which counts as critical; the rating comes from the researchers.

Advertisement

The Canadian Centre for Cyber Security describes the issue as a heap-based buffer overflow that can be triggered remotely without authentication. Possible outcomes include memory corruption, disclosure of sensitive information, crashes or code execution.

Who is affected: servers with AVX-512 VBMI

The flaw requires an x86-64 processor with the AVX-512 VBMI instruction set extension. Calif.io lists Intel Xeon starting with Ice Lake (Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids) and AMD EPYC and Ryzen starting with Zen 4. ARM64 systems are not affected.

In default configurations, the researchers achieved code execution without logging in on Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. With a login, it worked on Apache Kafka brokers, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Java programs that open a TLS connection to a malicious server are also at risk. The list is not exhaustive.

OpenJDK-based distributions are affected as well, including Amazon Corretto, Eclipse Temurin, Microsoft’s build, Azul Zulu, BellSoft Liberica, SAP SapMachine and Red Hat’s builds.

The Java builds that contain the fix

Oracle’s Critical Patch Update for November 2026 credits the two Calif.io researchers. The Canadian Cyber Centre lists the following Oracle builds as the versions to move to. For other distributions, check your vendor’s own advisory.

Advertisement
Java line Fixed build
Oracle Java SE 8 8u511b33-perf
Oracle Java SE 17 17.0.21.0.3
Oracle Java SE 21 21.0.13.0.3
Oracle Java SE 25 25.0.5.0.3
Oracle Java SE 27 27.0.1.0.3
Oracle GraalVM for JDK 17.0.21.0.3, 21.0.13.0.3

Builds listed in the alert of November 17, 2026. Source: Canadian Centre for Cyber Security, as of November 18, 2026.

One open question remains. The researchers point to OpenJDK 17.0.6 and later, while Oracle’s list also includes a Java 8 performance build. Whether older lines are affected isn’t clear from the sources we reviewed, so anyone running Java 8 should check with their vendor instead of assuming they’re safe.

How the disclosure unfolded

The research, the patch and the first government alert all came out on the same day. That gives administrators very little lead time.

Timeline

Java4Shell: from disclosure to fix

  1. Calif.io discloses Java4Shell

    The researchers publish their analysis of CVE-2026-114938 and score it 9.2 under CVSS 4.0.

  2. Oracle releases fixed builds

    The Critical Patch Update for November 2026 contains corrected Java SE and GraalVM builds.

  3. Canadian Cyber Centre issues alert AL26-029

    It lists the fixed builds and reports no known active exploitation.

Calif.io has released a harmless proof of concept that only writes inside a test array. The researchers say they’re holding back product-specific exploit chains until users have had time to patch.

How to check and protect your systems

The Canadian Cyber Centre recommends starting with an inventory of every Java runtime, including vendor and full build version, and prioritizing internet-facing systems. Third-party products, appliances and containers that bundle Java belong on that list too.

To find out whether a Linux server’s CPU has the relevant instructions, the researchers say the output of lscpu must show the flags avx512f, avx512bw, avx512vbmi and bmi2. If an update isn’t possible right away, both sources name a stopgap: the flag -XX:UseAVX=2 disables AVX-512 on x86-64 machines, and the researchers add -XX:-UseBASE64Intrinsics. Internet-facing applications that can’t be patched should be isolated from public networks until a fix is in place.

Frequently asked questions

Am I affected as a home user?

The researchers mainly describe server software. On the client side, they mention Java programs that connect over TLS to a malicious server. A processor with AVX-512 VBMI is also required.

How do I check whether my processor has AVX-512 VBMI?

On Linux, the output of lscpu must include the flags avx512f, avx512bw, avx512vbmi and bmi2, according to the researchers.

Is Java4Shell already being exploited?

As of November 17, 2026, the Canadian Centre for Cyber Security was not aware of active exploitation, and Upwind reported that the flaw was not in CISA’s Known Exploited Vulnerabilities catalog. A harmless test exploit is public.

What if I can’t update right away?

The sources name the JVM flags -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 (x86-64 only) as a stopgap. Internet-facing applications should be isolated from public networks where possible.

Your view: Do you know which Java versions run on your company’s servers, and how fast can you roll out a patch like this one? Share your experience in the comments.

Sources and date

As of: 11/18/2026

Transparency note: AI-assisted tools were used in researching, structuring and writing this article. The sources used are listed in the article. Publication takes place only after manual editorial approval.

Share this article

Comment Tell us what you think →

Leave a comment