Skip to main content
Black Friday: 40% off your first 3 months on any monthly plan with code BF40. Ends Dec 2.See the offer
Varaxon Technologies

Prioritization

Java4Shell (CVE-2026-114938): how to find affected Java and what to patch first

Java4Shell (CVE-2026-114938) from the OpenJDK, Oracle and CISA advisories: which Java and CPUs are affected, how to find hidden runtimes, and the fix order.

By Brandon Sooknanan, Founder, Varaxon Technologies · · 10 min read

Every few years a flaw lands in a piece of software so widely embedded that the first problem is not patching, it is working out where the software is. Java4Shell is one of those. The bug sits inside the Java runtime itself, so it reaches every Java application that decodes Base64 from an outside source on the right hardware, whether or not the application's own code is at fault.

This page sticks to what the primary sources say: the OpenJDK Vulnerability Group advisory, Oracle's entry for the CVE as published in the NVD, CISA's alert and the technical write-up from Calif, the firm that found it. We read them on 18 November 2026, with CISA's KEV catalog version 2026.11.17 and FIRST's EPSS scores for 18 November.

What Java4Shell is

Base64 is a way of writing binary data as plain text. Applications decode it constantly: login headers, web tokens, file uploads and messages between services all use it. To decode it faster, the HotSpot Java virtual machine uses special AVX-512 instructions on x86-64 processors that support them. Calif found that this fast path miscalculates the length of a short, padded final chunk, so a malformed string can make it write past the end of the buffer it was given.

Java rejects the bad input afterwards, but by then neighbouring memory may already be overwritten. Calif describes two outcomes: reading the application's memory, which can hold keys, tokens and personal data, and running the attacker's own code. It says each application needs its own exploit and a failed attempt can crash the application, but an attacker can often simply try again.

CVE-2026-114938 at a glance (sources read 18 November 2026)
ItemWhat the sources say
NameJava4Shell, given by Calif, which found and reported it
Disclosed and fixed17 November 2026 (OpenJDK advisory, Oracle patch update, CISA alert)
Where the bug isHotSpot JIT compiler, x86-64 Base64 decoding fast path
SeverityOracle: CVSS 3.1 score 8.1 (network, high attack complexity, no login needed). Calif: 9.2 under CVSS 4.0
WeaknessHeap-based buffer overflow (CWE-122)
CISA KEVNot listed as of catalog 2026.11.17
EPSS0.73% on 18 November 2026 (55th percentile)
Public codeCalif published a safe trigger that shows whether a runtime and CPU reproduce the bug. Its application exploits are withheld for now

Who is affected: three conditions

A system is exposed only when all three of these are true. That narrows the problem a lot, but each one is easy to get wrong if you guess instead of checking.

1. An affected Java runtime

The OpenJDK advisory marks the Java 17, 21, 25 and 27 release lines as affected by CVE-2026-114938, up to and including 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3. Calif says the bug arrived in OpenJDK 17.0.6. The OpenJDK advisory does not mark standard Java 8 or Java 11 for this CVE, but Oracle's own list includes its Java 8 Enterprise Performance Pack build 8u511b33-perf, and Oracle GraalVM for JDK 17 and 21 and GraalVM Enterprise Edition 21 are listed too.

Because the flaw is in OpenJDK code, Calif says the builds most organizations actually run are affected as well: Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine and Red Hat's OpenJDK, as well as Oracle's own. Each vendor publishes its fixed version on its own schedule.

2. An x86-64 processor with AVX-512 VBMI

The fast path only runs on processors that support AVX-512 VBMI. Calif names Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen processors on Zen 4 or newer. ARM64 systems are not affected. Many current servers and cloud instance types use these chips, so check rather than assume. On Linux this command, from Calif's write-up, must print all four flags for the processor to qualify:

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

3. An application that decodes outside Base64

Oracle says the flaw can only be exploited when an application passes untrusted data to the affected APIs, such as through a web service. In practice that covers most web applications: Calif reports code execution before sign-in on Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate in their default settings, and after sign-in on Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. It also reached sample apps built on Apache Struts and Spring Boot, and describes a client-side route where a Java program is attacked by a malicious server it connects to over TLS. Treat any internet-facing Java application as meeting this condition until its vendor says otherwise.

How to find every Java runtime

This is where most of the work is. CISA's alert makes the point directly: Java runtimes are often bundled inside third-party applications, container images and appliances, and may not appear as separate entries in a software inventory. A list of installed packages will miss them.

  1. Run credentialed scans. A scan that cannot log in sees open ports, not the Java version behind them, so it cannot tell you whether a server is affected. Check that each scan actually authenticated before you trust a clean result; our guide to credentialed vs non-credentialed scans shows what to look for. Make sure your scanner's checks have been updated since 17 November.
  2. Search the file system, not only the package list. On Linux, find / -xdev -name java -type f -perm -u+x 2>/dev/null lists every Java binary, including ones an application installed in its own folder; run each with -version. On Windows, look for every java.exe under the program folders. Many products install their own runtime; Atlassian's Jira and Confluence installers, for example, bundle one.
  3. Check containers and images. Run java -version inside each running container, and check the base image of every image you build or pull. A rebuilt image is the fix; patching the host does not change the runtime inside a container.
  4. Ask appliance and SaaS vendors. For appliances and hosted products you cannot inspect, the vendor's advisory is the only answer. Record who you asked and what they said.
  5. Record the CPU for each host using the command above, or the instance type for cloud machines. A server on ARM64 or an older x86 chip can be marked not exposed, with the evidence kept.

What to patch first

We normally rank findings with CISA's KEV list first, then EPSS, then CVSS. Java4Shell is a case where you should not wait for KEV. It is not on CISA's KEV list as of catalog 2026.11.17, and CISA's own early assessment recorded no known exploitation. But CISA has already issued an alert urging immediate patching, the finder reports working exploits against widely used products, and code that triggers the bug is public. EPSS, at 0.73%, cannot see any of that yet: across 2026, 81% of the CVEs CISA added to KEV had no EPSS score or one under 10% the day before they were listed.

  1. Internet-facing Java applications on affected CPUs, starting with the products Calif names as exploitable before sign-in: identity and single sign-on (Keycloak, PingFederate), Jira, Confluence, Jenkins and Artifactory. These hold credentials and secrets, and memory disclosure alone could leak them.
  2. Other internet-facing Java services that handle logins, tokens or file uploads.
  3. Internal Java services reachable by many users or systems, such as Kafka, Solr and Elasticsearch, which Calif reports as exploitable after sign-in.
  4. Java clients and batch jobs that connect out to servers you do not control, because of the client-side route Calif describes.
  5. Everything else on the normal patch cycle, including hosts that fail one of the three conditions, so a later hardware change does not reopen the hole.

If a server cannot be updated today, Calif names two Java start-up options that keep the vulnerable code from running: -XX:-UseBASE64Intrinsics turns off the fast Base64 path, and -XX:UseAVX=2 turns off AVX-512 entirely. The second is for x86-64 only; Calif warns that Java on ARM will not start with it. Neither option appears in the OpenJDK or Oracle advisories, so treat them as a stopgap, test them, and patch anyway. CISA also suggests validating and size-limiting Base64 input at the application boundary and limiting unauthenticated access.

Fixed versions

Oracle released fixed builds on 17 November 2026. For every other distribution, take the fixed version from that vendor's own advisory, and for a product with a bundled runtime, from the product vendor.

Oracle Java SE builds affected and fixed (Oracle's November 2026 Critical Security Patch Update and Java SE release notes)
Java lineAffected Oracle build (and earlier)Fixed Oracle build
Java 8 Enterprise Performance Pack8u511b33-perf8u513-perf
Java 1717.0.21.0.317.0.21.1
Java 2121.0.13.0.321.0.13.1
Java 2525.0.5.0.325.0.5.1
Java 2727.0.1.0.327.0.1.1

The OpenJDK advisory for 17 November lists nine other Java CVEs, plus one in JavaFX, fixed in the same release, so the update is worth taking on systems that fail the Java4Shell conditions too.

How to show you are clear

Clients, auditors and insurers will ask about Java4Shell by name. "We patched Java" is a claim. A short record per server is evidence:

  • Each Java runtime found, its path, its version before and after, and which application uses it.
  • The processor result for each host, so servers that were never exposed are documented as such.
  • The vendor answer for each appliance or hosted product you could not inspect.
  • A credentialed scan before and after the update, so the difference shows what changed. Our guide to proof of fix since the last scan explains how to present it.

Varaxon Scan Hub helps with the reporting side: it reads the exports from the scanners you already use, flags anything on CISA's KEV list, compares each rescan with the last one and writes a client-ready report of what was fixed and what is still open. It does not find Java runtimes on its own or replace the vendor updates. If CISA adds Java4Shell to its KEV list, any finding for it in your next upload moves to the top band automatically.

Common questions

What is Java4Shell?

Java4Shell is the name Calif gave to CVE-2026-114938, a memory-corruption flaw in the x86-64 Base64 decoding fast path of the HotSpot Java virtual machine. Malformed Base64 input can overwrite memory, which Calif shows can leak data or let an attacker run code. Fixes were released on 17 November 2026.

Is CVE-2026-114938 on CISA's KEV list?

Not as of CISA's 17 November 2026 update (catalog 2026.11.17). CISA did publish an alert the same day urging organizations to patch immediately. You can check its current KEV status, EPSS and CVSS together with our free CVE checker.

Are Java 8 and Java 11 affected by Java4Shell?

The OpenJDK advisory marks Java 17, 21, 25 and 27 as affected by CVE-2026-114938, not standard Java 8 or 11. Oracle's list does include its Java 8 Enterprise Performance Pack build 8u511b33-perf. Java 8 and 11 still received other security fixes in the same release.

Are ARM servers affected?

No. Calif says the vulnerable code runs only on x86-64 processors with AVX-512 VBMI, such as Intel Xeon Ice Lake and newer and AMD Zen 4 and newer. ARM64 systems are not affected.

Is there a workaround if I can't patch yet?

Calif names two Java start-up options: -XX:-UseBASE64Intrinsics, or -XX:UseAVX=2 on x86-64 only. Neither is in the OpenJDK or Oracle advisories. Use them as a temporary measure after testing, and apply the fixed Java build as soon as you can.

Turn your next scan export into a client-ready report.

Run a free pre-flight check

Cookie preferences

Essential site functions remain available whichever option you choose. Your advertising choice is saved on this site. The Scan Hub has a separate choice.

Google and Reddit may receive cookies, identifiers, browser and device information, and your network/IP information. Reject or withdraw at any time. Read the Privacy Policy.