Skip to content
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report
FrameFrame home

Your digital life. Back in your hands.

100% Canadian-owned · Support: support@frameprivacy.com

Product

  • Platform
  • Sample report
  • Breach Check
  • Frame agent
  • Extension
  • Mobile app
  • Pricing
  • Frame Business
  • Changelog

Resources

  • Blog
  • Help centre
  • Free leak test
  • Status
  • Data-broker catalog
  • RSS feed

Company

  • About
  • Our privacy promise
  • Contact
  • Press and brand

Legal

  • Legal hub
  • Privacy Policy
  • Terms
  • Security
  • Cookies
  • Accessibility

© 2026 Frame Labs Inc. All rights reserved.

en Englishfr Français
Your Privacy ChoicesSystem status

All posts

Research · 5 min read

Java4Shell: researchers show a 65-character Base64 string can corrupt memory in Java servers

Calif says a bug in OpenJDK’s fast Base64 decoder led to remote code execution in Jira, Jenkins, Keycloak and more. Patches are out. Other labs have reproduced crashes, not takeovers.

BBy Brody · FramePublished November 18, 2026
The OpenJDK logo on a light card with an orange edge, over a dark background.

On November 17, 2026, the security research firm Calif disclosed Java4Shell (CVE-2026-114938), a memory-corruption bug in the Base64 decoder of OpenJDK, the open-source code behind most Java runtimes. Oracle and the OpenJDK project released fixes the same day. Canada’s Cyber Centre and the U.S. agency CISA both issued alerts urging organisations to patch.

This is a story for anyone who runs Java servers, and for everyone else it is a good example of how to read a big vulnerability headline. Below, we separate what Calif demonstrated, what others have confirmed, and what is still unproven.

The bug, in plain terms

Base64 is a common way to turn binary data into text. Servers decode it constantly: login headers, single sign-on tokens, file uploads. To do it faster, Java uses hand-written machine code that relies on a set of instructions (AVX-512 VBMI) found on newer Intel Xeon and AMD Zen 4 or later processors.

Calif’s write-up explains that this fast path mishandles a malformed ending. For a 65-character input of 64 A characters and a single =, Java sets aside a 50-byte result, but the decoder writes 64 bytes, spilling past the end. Java does reject the input afterwards, but by then the neighbouring memory may already be overwritten. On older Java 17 builds the trigger is 128 A characters and =.

Because servers often decode Base64 before checking who you are, an attacker does not need an account to send that string.

What Calif says it demonstrated

  • Remote code execution without logging in against default setups of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate.
  • Remote code execution with a login against Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker.
  • Exploits against sample apps built on Apache Struts and Spring Boot, and a client-side exploit shared by another researcher, samczsun, where a Java program that connects to a malicious TLS server can be compromised.

Calif rates the bug 9.2 out of 10 under CVSS 4.0. It says the lists are not complete, and that there is no single exploit that works everywhere: each target needs its own memory layout and timing. Calif also says it used an AI coding assistant to find the bug. Its researcher Quang Luong writes that finding it took about an hour, the first working exploit two more hours, and the AI cost under US$200.

What others have confirmed, and what they have not

The Hacker News reports that Calif is holding back its attack code, and that other labs have so far reproduced crashes and a memory leak, but not code execution:

  • Upwind reproduced the memory corruption on an AWS server with an Intel Ice Lake chip, and it eventually crashed Java.
  • Blackpoint Cyber crashed a test Spring Boot app with about 28,300 malformed login requests in roughly 20 seconds, without logging in, and used Calif’s memory-read step to read a secret stored next to the overflow in all 30 local runs. It did not reproduce remote code execution.

Severity ratings differ. Oracle scores it 8.1 under CVSS 3.1 and calls it hard to exploit but requiring no login. Red Hat’s preliminary score is 9.8. Amazon describes the risk as a crash for unauthenticated users or, in some setups, code execution by a logged-in user.

On attacks: Canada’s Cyber Centre said it is "not aware of active exploitation at this time, but that can change quickly." The Hacker News says the bug was not in CISA’s list of known exploited vulnerabilities when it checked.

One more detail worth knowing: The Hacker News reports that a malformed input triggering the same overflow was posted publicly on September 9, in a proposed fix to OpenJDK that was later closed without being merged.

Who is exposed

  • Java versions: 17.0.6 and later on Java 17, and Java 21, 25 and 27. Standard Java 8 and 11 are not affected, except Oracle’s Java SE 8 Performance Pack build.
  • Hardware: only x86-64 processors with AVX-512 VBMI, such as Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newer. ARM64 chips, including Apple Silicon and AWS Graviton, do not run the vulnerable code.

That hardware detail means the same container image can be exposed on one server and not on another.

What to do if you run Java

  1. Update to a fixed build. OpenJDK and Oracle fixed it in 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Eclipse Temurin lists the same versions and is publishing binaries as testing completes. Amazon Corretto and Azul Zulu have fixed builds. Red Hat had not shipped fixes when The Hacker News checked.
  2. Restart Java and rebuild containers so the running process actually uses the new build. Products that bundle their own Java need an update from their maker.
  3. If you cannot update yet, start Java with -XX:-UseBASE64Intrinsics to turn off the fast Base64 code, or -XX:UseAVX=2 on x86-64 only. Calif and the Cyber Centre both list these. Remove them once patched.
  4. Prioritise internet-facing systems, and look for bursts of Base64 decoding errors or unexplained Java crash logs, which Upwind suggests as signs of attempts.

If you do not run servers, there is nothing for you to do except keep the apps and devices you use up to date.

How Frame helps

This is a server software vulnerability, not a breach of personal data, so there is nothing to look up for it. Frame can also look up your verified emails in Have I Been Pwned’s breach database whenever you want to check what has leaked. If a service later reports a breach tied to this bug, we will write about it here.

Related coverage

  • Check Point says attackers used PHP2Shell, then wiped some VMware hosts: Calif’s previous disclosure, PHP2Shell, and what happened when attackers picked it up.

Sources

  • Calif, Java4Shell: Write once, RCE everywhere, November 17, 2026
  • Canadian Centre for Cyber Security, AL26-029: Critical vulnerability impacting Oracle Java, CVE-2026-114938, November 17, 2026
  • CISA, Critical Java Vulnerability Requires Immediate Patching, November 17, 2026
  • Adoptium, Eclipse Temurin guidance for CVE-2026-114938 "java4shell", November 18, 2026
  • The Hacker News, Java4Shell Flaw (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak and More, November 18, 2026
More in Research

More stories

  • ResearchResearchers planted fake keys in public container images. Bots used the first one in 8 secondsNovember 19, 2026 · 4 min read
  • MalwareSpies behind EggStreme rebuilt their malware within weeks of being exposed, Bitdefender saysNovember 19, 2026 · 4 min read
  • ResearchResearchers reset the TPM’s wrong-PIN counter to guess Windows Hello and BitLocker PINs in daysNovember 19, 2026 · 5 min read

New posts, by email.

About once a month. Plain-language privacy notes, nothing else. I never share your address.

Sent by Frame · privacy@frameprivacy.com · Privacy Policy

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report