Java4Shell fixes arrive unevenly across Java distributions
Oracle and OpenJDK 27 have patched the HotSpot Base64 flaw, but other Java lines and vendor builds lag, and security firms disagree on how easily it leads to takeover.
- What happened
- Oracle and the OpenJDK project released fixes for the Java4Shell flaw, CVE-2026-114938, in the HotSpot JVM's AVX-512 Base64 decoder.
- What’s new
- Patched builds exist for Oracle Java SE and OpenJDK 27, but as of 17 November public OpenJDK 17, 21 and 25 update repositories lacked the fix.
- Why it matters
- Administrators running Java 17.0.6 or later on recent Intel and AMD servers must track separate vendor patches, and Calif says popular enterprise apps can be taken over.
Oracle and the OpenJDK project have released fixes for Java4Shell (CVE-2026-114938), the HotSpot Base64 decoder flaw that CISA urged organisations to patch immediately, but fixed builds are not yet available for every Java line. Security firms also differ on how readily the bug can be turned into a full server takeover.
Where the patches stand
Oracle shipped its fixes in its November 2026 Critical Security Patch Update, which addresses 11 Java SE vulnerabilities, SecurityWeek reports. According to Endor Labs, the OpenJDK fix is a four-line change tracked as JDK-8393212 under the title Base64 optimization improvements, and it is present in OpenJDK 27.0.1.1 and mainline. Endor Labs says that as of 17 November the change had not reached the public update repositories for Java 17, 21 and 25.
Endor Labs notes that distributions such as Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK and Red Hat's build will each publish fixed versions on their own timetable, and advises reading each vendor's advisory rather than inferring version numbers from Oracle's. Until an update is available, Endor Labs says a JVM setting can switch off the vulnerable code.
Exposure depends on hardware as well as version. Calif, the firm that found the bug, says OpenJDK 17.0.6 and later are vulnerable; Endor Labs adds that every release from 18 onward is too, while Java 8 and 11 are not. Exploitation needs x86-64 processors with AVX-512 VBMI, such as Intel Xeon chips from Ice Lake onward and AMD Zen 4 or newer, according to SecurityWeek. ARM64 systems are not affected.
Which applications Calif says it compromised
Calif says it achieved remote code execution without authentication against Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate in default configurations, and with authentication against Apache Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Calif stresses there is no universal exploit, since each application needs its own route to the decoder. Its public proof of concept shows the memory corruption only; the company is holding back its working attack chains until users have upgraded. Endor Labs lists these product results as claims by Calif, with no public proof-of-concept shell.
How hard exploitation is
Calif rates the flaw 9.2 under CVSS 4.0. SecurityWeek reports that Oracle's advisory scores it 8.1 under CVSS 3.1, classing it as attackable over a network without logging in, though difficult to pull off. Endor Labs says no vector string has been published for the CVE.
Endor Labs' own reproduction found the decoder writes 62 or 63 bytes of a fixed value past the end of its buffer, so an attacker influences the location of the write but not its contents. On its own, Endor Labs says, that typically crashes the JVM, amounting to an unauthenticated denial of service. VulnCheck reports that crashing a vulnerable JVM was easy in its tests and that it built a full code-execution exploit, but says that requires per-target heap manipulation and an ASLR bypass. VulnCheck said "we don’t anticipate that CVE-2026-114938 will be easily or widely exploitable", while expecting attackers to find narrow paths in specific applications.
Cisco Talos has not seen the flaw exploited in the wild but expects probing to increase after disclosure, SecurityWeek reports. For detection, Endor Labs suggests flagging Base64 input that ends in = or == but whose length is not a multiple of four.