Java4Shell CVE Patch Alert: CISA Urges Immediate Patching for Critical Java Flaw

November 18, 2026
4 mins read
Rows of rack servers with status lights in a data centre, the infrastructure that runs enterprise Java.
Server racks at the NOIRLab headquarters computer server room in Tucson, Arizona. Photo: NOIRLab/NSF/AURA/T. Slovinsky, CC BY 4.0.
If your company runs Java 17 or newer on a recent Intel Xeon or AMD EPYC server, a Java4Shell CVE-2026-114938 patch alert may matter to you. Attackers can send specially crafted data that crashes Java software and, in some setups, runs their own code, all without logging in. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) issued an alert on November 17, 2026, telling organizations to patch now. The alert covers CVE-2026-114938, which CISA calls “a critical memory-corruption vulnerability, known as ‘Java4Shell.'” The flaw sits in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine. That is the engine that runs Java programs. That engine runs Java programs. Base64 is a common way to encode binary data as ASCII text, and it appears in logins, file attachments and web tokens. Oracle rates the flaw 8.1 (High) under CVSS v3.1, a 0-to-10 severity scale, in its November 2026 advisory. Red Hat gives a preliminary 9.8 (Critical) under CVSS v3.0 in its security bulletin. Calif, the firm that reported the bug, scores it 9.2 (Critical) under CVSS v4.0. CIRCL, Luxembourg’s incident response center, says OpenJDK and Oracle released security updates on November 17, and Canada’s cyber centre issued its own alert. For IT and DevOps teams, the risk extends beyond the Java versions you installed on purpose. It covers the same class of hidden enterprise software behind other security test failures. Java often ships inside container images, vendor appliances and third-party applications. CISA warns that those runtimes may not appear as separate entries in software inventories. Until every copy is patched or protected, any internet-facing service that accepts Base64 input may be exposed. That gap resembles the client data exposures vendors disclose after a breach.

Why AVX-512 VBMI Matters and ARM64 Is Spared

The bug only affects processors that support wide vector instructions called AVX-512 VBMI. These instructions process many bytes at once, which is why Java can use them to decode Base64 faster. Java typically switches to this accelerated decoder after its compiler optimizes the code, and that faster path contains the flaw. Chips without these instructions take a different path. Red Hat says ARM64 systems are not known to be affected. Red Hat’s examples of affected x86-64 chips include Intel Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, plus AMD Zen 4 and later. The gap between the two main scores appears to come from how hard it is to reach the vulnerable path. Oracle rates attack complexity as high, while Red Hat rates it low. An attacker needs a CPU with the right instructions, and the Java compiler must select the affected decoder. Red Hat marks its 9.8 score as preliminary, a caution worth noting alongside the software defect that disrupted UK flight control. Researchers also disagree on how far attackers can go. VulnCheck says crashing an affected JVM is straightforward. Remote code execution, it says, needs heavy work. That includes heap grooming, which arranges memory into a predictable layout, plus a separate way to leak memory addresses. CIRCL says code execution depends on the application and is not universal. CISA’s alert says the flaw could allow unauthenticated remote code execution.

Affected Versions and Fixed Builds

Upstream OpenJDK 17.0.6 and later builds are affected until patched, along with OpenJDK 21, 25 and 27. Red Hat says standard OpenJDK 8 and 11 are not affected by this decoder. Oracle’s Java 8 Enterprise Performance Pack build, 8u511b33-perf, is affected, and CIRCL gives 8u513-perf as the fixed build. CIRCL lists fixed upstream builds of 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Vendor builds differ, so check the release notes from your provider, such as Amazon Corretto, Eclipse Temurin, Azul or Red Hat. Oracle’s affected builds are listed in its November 2026 Critical Security Patch Update.

CISA and Vendor Remediation Checklist: Patch First, Then Add Controls

Inventory every Java runtime, including JDKs inside container images, appliances and third-party applications. Patch internet-facing systems first, using the fixed build from your Java vendor. On Linux, check whether the CPU supports AVX-512 VBMI by running `grep avx512vbmi /proc/cpuinfo`. If patching must wait, start Java with `-XX:-UseBASE64Intrinsics`, which disables only the accelerated Base64 decoder. CIRCL prefers it to `-XX:UseAVX=2`, which turns off AVX-512 more broadly and can affect performance. Validate Base64 input and enforce size limits in your application, as CISA recommends. Watch for unexpected JVM crashes and Java processes you do not recognize. A web application firewall or reverse proxy is not a general fix, CIRCL warns. Neither flag removes the vulnerable code, so the security update remains the permanent fix. Java4Shell applies only to x86-64 processors with AVX-512 VBMI, but many servers run those chips. Find your Java runtimes, patch internet-facing systems first, and use the Base64 flag where updates must wait. Scores and researchers’ views on code execution still differ, so watch Oracle, Red Hat and your Java vendor’s advisories for updates.

Rahul Somvanshi

Rahul, possessing a profound background in the creative industry, illuminates the unspoken, often confronting revelations and unpleasant subjects, navigating their complexities with a discerning eye. He perpetually questions, explores, and unveils the multifaceted impacts of change and transformation in our global landscape. As an experienced filmmaker and writer, he intricately delves into the realms of sustainability, design, flora and fauna, health, science and technology, mobility, and space, ceaselessly investigating the practical applications and transformative potentials of burgeoning developments.

Leave a Reply

Your email address will not be published.

Exterior view of the brutalist concrete facade of the FBI J. Edgar Hoover Building headquarters in Washington, D.C.
Previous Story

FBI Warns Autonomous ARTEX AI Tool Breaches Enterprise Networks in Under Three Hours Across 1,600 Exposed Consoles

Latest from News

Don't Miss