Many business tools, including Jira, Jenkins, and login systems, are built on a technology called Java. Java has a built-in helper that unpacks coded text. A newer, faster version of that helper has a counting mistake. When it is fed a deliberately odd piece of text, it writes data outside the space set aside for it. Think of a delivery driver who runs out of room in your storage unit and dumps the extra boxes in your neighbour’s unit. Attackers can use that mess to crash a system, peek at private data, and, researchers say, in some cases take control of it. What makes it serious is that the trick can work before anyone logs in. What makes it manageable is that a fix is already available.

Should You be Worried?

  • Your company runs Java 17 or newer on recent Intel or AMD servers: possibly yes. Ask your IT team.
  • You’re not sure: ask IT one question: “Do we run Java 17 or newer, and have we installed the November 17 update?”
  • You only run older Java (8 or 11), or ARM-based servers: this particular bug doesn’t apply.

Java4Shell (CVE-2026-114938) – Highlights

ParticularsHighlights
What it isA memory bug in the fast Base64 decoder inside OpenJDK 17.0.6 and later, including Java 21, 25 and 27
Who is exposedOnly servers on x86-64 chips with AVX-512 VBMI. The same app can be safe on one machine and exposed on the next.
How badResearchers at Calif say they got code execution on six popular apps, including Jira, Jenkins, and Keycloak, without a login. 
What to doPatch Java now. If you can’t, one JVM flag (command-line options passed to the java launcher to configure memory, garbage collection, diagnostics, and runtime behavior) switches off the vulnerable code.

Your Jira, your Jenkins and your login server all do one small, boring thing thousands of times a day: they decode Base64 text. Java4Shell (CVE-2026-114938) turns that boring step into a way in. Oracle and the OpenJDK project shipped fixes on November 17, 2026, the same day Calif published how the bug works. 

What is Java4Shell?

Java4Shell is the nickname for CVE-2026-114938, a memory-corruption flaw in OpenJDK’s hardware-accelerated Base64 decoder. When it reads a specially malformed string, it writes about 62 bytes past the end of its buffer. Researchers say attackers can turn that into a memory leak and, in some apps, remote code execution.

Calif, the security firm that found and reported it, gave it the name. The bug had a rough few weeks before the fix: a public OpenJDK pull request from September 9 described an overflow in the same code, and its author closed it in early November after it sat idle for more than eight weeks. Details also leaked ahead of the patch on November 17.

How the Java4Shell bug works?

Picture a packing station with a box that holds 50 items. A new, faster machine packs 64 items at a time. Usually that’s fine. But if the input ends in an odd way, the machine miscounts and still stamps all 64 items in. The extras spill into the next box, which belongs to someone else. In Java, that “next box” is another piece of the application’s memory.

Here is how one odd character turns into a problem:

  1. Servers unpack coded text all day. This coded text (Base64) hides in things like login details and security tokens. Servers often unpack it before checking who you are, so an attacker doesn’t need an account.
  2. Java switches to a faster tool. When the unpacking happens a lot, Java swaps in a speed-boosted version. It only does this on newer server chips.
  3. One odd character causes the mistake. If the text ends with an extra “=”, the faster tool miscounts and writes about 62 bytes of data outside its space. Java then rejects the text as invalid, but the extra data is already out there.
  4. The attacker can’t choose what gets written. They can only influence where it lands. That’s why early experts thought the worst result would be a crash.
  5. Calif found a clever workaround. They arranged things so the overflow makes a neighbouring storage area look bigger than it is. That lets them read memory they shouldn’t see, such as passwords or keys (they call this JavaBleed). Calif says more steps can then lead to running their own code.

One caution: there is no single attack that works everywhere. Each target needs its own careful setup, and a failed attempt can crash the system. The attacker can often just try again.

Who is affected by Java4Shell?

You need three things to line up: a vulnerable Java build, a specific kind of chip, and an app that decodes Base64 from outside.

CheckAffectedNot Affected
Java VersionJava 17.0.6 and later on the 17 line, plus Java 21, 25 and 27, before the fixed builds. Oracle’s Java SE 8 Performance Pack (8u511b33-perf) and GraalVM for JDK 17 and 21 are also listed.Standard Java 8 and Java 11 builds
Chipx86-64 with AVX-512 VBMI: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newerARM64 chips (for example AWS Graviton) and older Intel or AMD chips
App BehaviourAnything that sends outside Base64 text through Java’s standard decoder, such as login headers and tokensApps that never decode attacker-supplied Base64

Because the vulnerable code only runs on certain chips, the same container image can be exposed on one server and safe on another. On Linux, this command shows whether a server has the four CPU features the bug needs. All four must appear in the output:

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

Calif says Java clients are at risk too. A Java program that connects to a malicious TLS server can be compromised even if it runs no service of its own. That exploit came from another researcher, samczsun, and the route to the decoder has not been published.

Which popular tools did the researchers test?

Calif says it was able to run its own code on these tools without needing a login, using their default settings:

  • Keycloak: a login and single sign-on tool
  • Atlassian Jira: project and task tracking
  • Atlassian Confluence: a team wiki for documents
  • JFrog Artifactory: a store for software packages
  • Jenkins: a tool that builds and ships software
  • PingFederate: another single sign-on tool

It reports the same result for the tools below, but there the attacker first needs a login:

  • Apache Kafka Broker: moves data between systems
  • Apache Solr and Elasticsearch: search engines for company data
  • Gerrit: a tool for reviewing code
  • Spinnaker: a tool for releasing software

Calif says these lists are incomplete, so please don’t treat them as a safe list. Any Java-based tool that handles coded text is worth checking.

“Securing Organizations Since 2013”

Rated 4.9/5 on Gartner Peer Insights, 4/5 on G2 and 4.5/5 on Trustpilot

Book Your Free Cybersecurity Consultation Today!

*By clicking submit, you agree to our T&C, consent to our privacy policy.

How to Fix Java4Shell?

The real fix is to update to your vendor’s patched build, then restart. Here is where each vendor stood on November 18, 2026:

Vendor/buildFixed releaseStatus
Oracle Java SE 1717.0.21.1Released Nov 17
Oracle Java SE 2121.0.13.1Released Nov 17
Oracle Java SE 2525.0.5.1Released Nov 17
Oracle Java SE 2727.0.1.1Released Nov 17
Oracle Java SE 8 Performance Pack8u513Released
Oracle GraalVM for JDK / Enterprise Edition17.0.21.1, 21.0.13.1 / 21.3.20.1Released
Amazon Corretto17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4Released
Azul Zulu (free builds)17.70.201, 21.54.201, 25.38.201, 27.30.201Released
SapMachine17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1Released, but release pages don’t say what they fix
Red Hat Enterprise Linux 8, 9, 10 and Red Hat build of OpenJDK 17, 21, 25None yetFix pending
Eclipse Temurin, Microsoft Build of OpenJDK, BellSoft LibericaNot listedCheck your vendor

Three things people forget:

  • Bundled Java. Products that ship their own Java runtime need an update from the product’s maker, not just from you.
  • Restart. A patched JDK on disk does nothing for a service that is still running the old one.
  • Containers. Rebuild and redeploy images so the running process uses the new build. For Red Hat-based images, that means once updated images are out.

Vendor status changes quickly, so check your vendor’s advisory today rather than relying on this table.

Can’t Patch Today? Here’s What to Look For

If you can’t update yet, start the JVM with one of these flags and remove it once the fixed build is installed:

  • -XX:-UseBASE64Intrinsics switches off only the fast Base64 code. It removes the vulnerable path and leaves other AVX-512 speedups alone. This is the gentler option.
  • -XX:UseAVX=2 switches off AVX-512 entirely. Use it only on x86-64 servers. Java on ARM64 doesn’t recognise it and won’t start.

The security firm Upwind tested both settings and found that each one stopped the problem on every affected Java version it tried. It also warns about a third setting, -XX: DisableIntrinsic=_base64_decodeBlock. Used on its own, it stops Java from starting at all, so avoid it.

Some companies put a “gatekeeper” server in front of their apps that waits for each request to arrive in full before passing it on. That blocks some attacks but not all. Think of it as a speed bump, not a fix.

Signs to look for in your logs

None of these prove a compromise, and not seeing them doesn’t prove you’re safe. But they are worth a search today:

  • Base64 tokens of 32 characters or more that end in = and whose length isn’t a multiple of 4, especially in Authorization headers
  • Bursts of IllegalArgumentException errors from java.util.Base64$Decoder
  • Unexplained hs_err_pid crash logs, or bursts of service restarts

Get in touch with Kratikal now!

Cyber Security Squad – Newsletter Signup

Java4Shell FAQ

  1. What is Java4Shell?

    It’s the nickname for CVE-2026-114938, a memory bug in OpenJDK’s fast Base64 decoder. It lets a malformed string write past the end of a buffer, which can crash Java, leak memory and, according to researchers, lead to code execution.

  2. Which Java versions are vulnerable to Java4Shell? 

    Java 17.0.6 and later on the 17 line, plus Java 21, 25 and 27, before the fixed builds (17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 for Oracle). Standard Java 8 and 11 are not affected, but Oracle’s Java 8 Performance Pack is.

  3. Do ARM servers need to worry? 

    No. The vulnerable code only runs on x86-64 chips with AVX-512 VBMI, so ARM64 machines such as AWS Graviton don’t run it. They still need patching for other Java fixes in the same release.

  4. Is Java4Shell being exploited in the wild? 

    Not as of November 18, 2026. No attacks have been reported, and it wasn’t in CISA’s KEV catalog at last check. Crashes and memory leaks have been reproduced by independent labs; code execution is claimed by Calif but not yet reproduced by others.

  5. How do I protect myself if I can’t patch right away? 

    Start Java with -XX:-UseBASE64Intrinsics, which turns off the vulnerable fast path. Or use -XX:UseAVX=2 on x86-64 servers only. Remove the flag after you patch.

  6. My app has no login page. Am I safe? 

    Not automatically. Servers decode Base64 in many places before they check who you are, and a Java client that connects to a malicious TLS server can also be affected, per Calif. Check the Java version and the chip instead of assuming.