Skip to content

AI & tech update

Java4Shell (CVE-2026-114938): what to check and patch this week

A critical flaw in Java's Base64 decoder can crash servers and, in some setups, allow remote code execution. Here is who is affected, which versions fix it and what to do if you cannot patch today.

Muhammad BilalFounderPublished 4 min read

On 17 November 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) published an alert asking organisations to patch a critical Java vulnerability straight away. It is tracked as CVE-2026-114938 and has been nicknamed Java4Shell. Oracle and the OpenJDK project released fixed builds the same day.

If your business runs any software built on Java, including tools you bought rather than built, this is worth an hour of someone's time this week.

Note: This article was written on 20 November 2026. Vendor advisories change as new builds ship, so check the sources at the end before acting.

What the flaw is

The bug is in the part of the Java Virtual Machine (the HotSpot JVM) that decodes Base64, a common way of turning binary data into plain text so it can travel inside JSON, emails, tokens and web requests. According to CISA, specially crafted Base64 input can crash the JVM and can allow unauthenticated remote code execution: an attacker who never logs in could, in the worst case, run their own code on your server.

Base64 decoding happens in a lot of places that nobody thinks about: login tokens, file uploads, API payloads. That is why the alert is broad.

Who is affected

Two things both have to be true.

1. An affected Java version

Security researchers and Oracle list these release lines as affected:

Release lineAffectedFixed in (Oracle / OpenJDK numbering)
Java 1717.0.6 and later, up to 17.0.21.0.317.0.21.1
Java 21up to 21.0.13.0.321.0.13.1
Java 25up to 25.0.5.0.325.0.5.1
Java 27up to 27.0.1.0.327.0.1.1
Java 8 Enterprise Performance Pack8u511b33-perf8u513-perf

Standard Java 8 and Java 11 builds are not listed by OpenJDK as affected. Other distributions (Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Liberica, Red Hat and others) use their own version numbers, so check each vendor's advisory rather than comparing numbers with the table.

2. A processor with AVX-512 VBMI

The vulnerable code path only runs on x86-64 processors that support the AVX-512 VBMI instruction set. ARM64 machines, such as AWS Graviton servers and Apple Silicon Macs, are not affected. On Linux you can check whether a machine qualifies by looking for the avx512f, avx512bw, avx512vbmi and bmi2 flags in /proc/cpuinfo. All four must be present.

This narrows the risk a lot, but cloud servers move between hardware generations, so "we checked one machine" is not the same as "we are safe".

How serious is it right now?

  • Oracle rates it 8.1 (CVSS 3.1), with high attack complexity. One research group rates it 9.2 under CVSS 4.0.
  • As of 18 November, GreyNoise had seen exploitation attempts but no confirmed successful attacks against its sensors.
  • A public proof of concept shows the crash, not a full takeover. Some security firms say they have working exploits that are not public.

In plain terms: crashing a vulnerable server looks easy, and full remote code execution looks hard but possible. Crashes alone are enough to take a customer-facing service down.

What to do this week

  1. Make a list of everything that runs Java. Include the obvious (your own backend) and the hidden: Java bundled inside third-party products, Docker images, build servers, search engines like Elasticsearch, identity servers like Keycloak and network appliances. CISA specifically warns that bundled runtimes may not show up in your software inventory.
  2. Patch internet-facing systems first. Update to a fixed build from your Java vendor and rebuild container images, not just the host.
  3. Ask your software vendors. If a product you pay for ships its own Java, ask whether they are affected and when a fix is coming. Write the answer down.
  4. Watch for crashes. Unexpected JVM crashes or restarts on public services are a sign someone is probing.

If you cannot patch today

Security researchers have described two temporary JVM startup flags. Neither Oracle nor the OpenJDK advisory mentions them, so treat them as stop-gaps and test before using them in production:

  • -XX:-UseBASE64Intrinsics turns off the optimised Base64 code path. Keycloak recommends this as an interim mitigation.
  • -XX:UseAVX=2 turns off AVX-512 instructions entirely. It only works on x86-64; Java on ARM will refuse to start with it.

CISA also suggests validating and size-limiting Base64 input at the edge of your application and limiting what unauthenticated users can reach.

A wider lesson for small teams

Most businesses learn about flaws like this from a news story, days late. A short, maintained list of the software you run, the versions and who is responsible for updating each one turns "are we affected?" from a two-day scramble into a ten-minute check. If you do not have that list, this week is a good time to start it.

Sources

  1. Critical Java Vulnerability Requires Immediate Patching, CISA ()
  2. Critical Security Patch Update – November 2026, Oracle ()
  3. Java4Shell (CVE-2026-114938): Frequently asked questions about OpenJDK RCE vulnerability, Tenable

Try it yourself

Not sure what runs Java in your stack?

We can review your servers, containers and vendor software, apply the fixes and leave you with an up-to-date inventory.

Keep reading