Java4Shell flaw CVE-2026-114938 in OpenJDK can lead to remote code execution, and CISA urges immediate patching
TLDR
- Calif disclosed Java4Shell, CVE-2026-114938, a memory-corruption flaw in OpenJDK's Base64 decoder that can lead to remote code execution.12
- Oracle shipped fixes on 17 November, and CISA urged organisations to patch immediately, prioritising internet-facing systems.15
- CyberScoop and Endor Labs report no exploitation in the wild and no CISA KEV listing as of 17 November.68
Security firm Calif disclosed a critical vulnerability in OpenJDK on Tuesday 17 November 2026, dubbed Java4Shell and tracked as CVE-2026-114938, BleepingComputer reports.1 It is a memory-corruption flaw in Java's hardware-accelerated Base64 decoding that can be exploited to disclose information from memory or achieve remote code execution.1 CISA's alert of the same day strongly urges organisations to patch immediately and says specially crafted Base64 input could crash the JVM and allow unauthenticated remote code execution.5 Oracle released patches on 17 November in its November Critical Security Patch Update; Oracle's advisory and BleepingComputer put the update at 655 security patches, while CyberScoop says 652.146 The Hacker News reported that day that Calif said on X the flaw had leaked, and that Calif planned to publish technical details by 1pm Pacific time after Oracle released a patch.7
Calif says the corruption can be triggered by 64 "A" characters followed by a single equals sign, or 128 on older OpenJDK 17.2 BleepingComputer reports the flaw affects OpenJDK 17.0.6 and later and distributions built from it, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.1 The OpenJDK advisory lists CVE-2026-114938 as affecting versions 17, 21, 25 and 27, and not 8 or 11, although Calif's list of Oracle builds affected includes Java SE 8u511b33-perf.23 It runs only on x86-64 processors with AVX-512 VBMI support, and CyberScoop reports ARM64 systems are unaffected.16 Calif says it demonstrated unauthenticated code execution in Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate in default configurations, and authenticated code execution in Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker.2 Calif says there is no universal exploit, and BleepingComputer reports it has published a proof of concept showing the memory corruption but not its weaponised exploits.12 Calif says researcher Quang Luong found the bug in about an hour using AI and built a first working exploit in two more, at a token cost under $200.2
Calif rates it 9.2 under CVSS 4.0, while Oracle assigned 8.1 under CVSS 3.1, the same score shown in the OpenJDK advisory.13 VulnCheck says its team reproduced the bug on Ice Lake hardware, that triggering a JVM crash takes repeated crafted requests but is otherwise trivial where input reaches the vulnerable decoder, and that code execution needs non-trivial heap grooming and a target-specific memory disclosure path.9 It also says a full remote code execution exploit was available to its Initial Access Intelligence customers from 6pm Eastern on 17 November.9 Datadog likewise says denial of service is the more readily achievable impact and that reliable code execution needs application-specific work.10 Earlier on 17 November, The Hacker News reported that analyses by Upwind and Equixly of the OpenJDK source pointed to a JVM crash as the likely result, and that neither firm said it had reproduced the overflow on AVX-512 hardware.7
BleepingComputer reports Calif recommends launching OpenJDK with -XX:-UseBASE64Intrinsics, or -XX:UseAVX=2 on x86-64 systems, as temporary mitigations until the runtime is updated.1 Datadog says the second flag prevented the out-of-bounds writes in its tests and fails to start on ARM64 JVMs, and lists the first fixed Oracle releases as 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.10 Endor Labs says the fix is JDK-8393212, committed on 14 October under embargo as "Base64 optimization improvements", and present in OpenJDK 27.0.1.1; it says the public jdk17u, jdk21u and jdk25u repositories did not yet carry it on 17 November.8 CISA's alert advises reviewing software inventories for JDKs and runtimes bundled with third-party applications, container images and appliances, applying Java and vendor patches as soon as they are available, and, where patching is not feasible, restricting and validating Base64 input at the application boundary.5 CyberScoop reports no exploitation in the wild had been reported at publication and that none of the related CVEs had been added to CISA's Known Exploited Vulnerabilities list, and VulnCheck likewise says it is not known to be exploited in the wild.69
Why it matters: a runtime flaw that CISA says could allow unauthenticated remote code execution may sit inside bundled JDKs in third-party applications, container images and appliances, where CISA notes inventories may not list it separately.5
Sources
- Critical Java4Shell flaw allows RCE attacks on major Java applications (BleepingComputer)
- Java4Shell: Write once, RCE everywhere (Calif)
- OpenJDK Vulnerability Advisory: 2026/11/17 (OpenJDK Vulnerability Group)
- Oracle Critical Security Patch Update Advisory - November 2026 (Oracle)
- Critical Java Vulnerability Requires Immediate Patching (CISA)
- A vulnpocalypse bug worthy of attention: Researchers disclose critical flaw in Java with help of AI (CyberScoop)
- Oracle to Patch 11 Java Flaws Today as Critical OpenJDK RCE (CVE-2026-114938) Report Emerges (The Hacker News)
- Java4Shell (CVE-2026-114938): Pre-Auth Heap Overflow in OpenJDK (Endor Labs)
- Java4Shell CVE-2026-114938: Fine, I Guess We'll Do This Again (VulnCheck)
- Java4Shell: Remote Code Execution in OpenJDK (CVE-2026-114938) (Datadog Security Labs)