IntroductionOn November 17, 2026, security researchers from Calif.io publicly disclosed Java4Shell (CVE-2026-114938, CVSS v4.0: 9.2 Critical), a severe heap memory-corruption vulnerability in OpenJDK’s hardware-accelerated (intrinsic) Base64 decoder on certain CPUs. The disclosure coincided with coordinated advisories from the OpenJDK Vulnerability Group and Oracle’s November 17, 2026 security patch release.Because Base64 decoding is foundational to network protocols, this runtime-level vulnerability can be reached in enterprise applications that pass attacker-controlled input to the affected decoder. Calif.io demonstrated pre-authentication Remote Code Execution (RCE) in default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate. Additionally, post-authentication RCE was achieved in Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Netflix Spinnaker, as well as a client-side TLS exploit affecting Java clients connecting to a malicious server. Immediate patching for affected environments is strongly recommended, alongside other mitigation steps outlined in this advisory. Zscaler’s security team is actively analyzing this issue across both production and corporate environments. We will continue to update the Zscaler Trust post and this advisory as new information becomes available. RecommendationsOrganizations running Java workloads on x86-64 infrastructure should take the following actions:Apply vendor patches immediately: Upgrade OpenJDK, Oracle Java SE, Oracle GraalVM, and all downstream OpenJDK distributions to the patched builds released on or after November 17, 2026 (such as Oracle Java SE 17.0.21.1, 8u513, 21.0.13.1, 25.0.5.1, and 27.0.1.1 security updates) and restart all running JVM processes and containers.Apply JVM flag workarounds where patching is delayed: If an immediate JDK upgrade is not feasible, defenders can completely disable the vulnerable assembly code path by passing either of the following flags at JVM startup (e.g., via JAVA_TOOL_OPTIONS or JDK_JAVA_OPTIONS):-XX:-UseBASE64Intrinsics (Recommended): Disables hardware-accelerated Base64 encoding and decoding intrinsics across all architectures, falling back to safe Java bytecode execution.-XX:UseAVX=2 (x86-64 hosts only): Restricts HotSpot to AVX2 instructions, preventing the use of AVX-512 VBMI instructions. Warning: Use this flag only on x86-64 machines; OpenJDK on ARM64 does not recognize this flag and will fail to start.After adjusting startup command lines and parameters, restart all running JVM processes and containers.Check Host CPUs for AVX-512 VBMI Exposure: Because CVE-2026-114938 is hardware-dependent, administrators can determine if the CPU of a Linux system is capable of executing the vulnerable Base64 decoder by inspecting the /proc/cpuinfo file and determining if all four of the following flags are present: avx512f, avx512bw, avx512vbmi, and bmi2. If a system is not susceptible, the JVM patches should still be applied in accordance with local policy and best practices.Eliminate public exposure: Place internet-facing Java applications (such as Keycloak, Jira, Confluence, Jenkins, Artifactory, and PingFederate) behind Zscaler Private Access (ZPA).Enable reverse-proxy request buffering (Defense-in-Depth): Many remote heap grooming techniques rely on partial HTTP requests to prepare the heap for successful exploitation. Enabling full HTTP request-body buffering at the reverse proxy (e.g., Nginx proxy_request_buffering on;) disrupts multi-connection timing alignment—though note this is not a complete mitigation for single-request chains (such as Elasticsearch) or upgraded WebSocket tunnels. Affected JDK Distributions And VersionsCVE-2026-114938 affects OpenJDK 17.0.6 and newer, as well as specific performance/patch builds across Oracle Java SE and downstream OpenJDK distributions as shown in the table below:Vendor / CategoryAffected Products & VersionsRemediation / PatchOpenJDK (Upstream)OpenJDK 17.0.6 and newerApply OpenJDK 2026-11-17 advisory patches, or if patching is delayed, use -XX:-UseBASE64Intrinsics as a temporary workaround.Oracle Java SE / Oracle GraalVM8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3 (and prior unpatched builds with the affected Base64 decoder)Upgrade to the applicable Oracle November 17, 2026 patch (e.g., Java SE 17.0.21.1).Downstream OpenJDK DistributionsAmazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDKUpgrade to a build that fixes CVE-2026-114930, or if patching is delayed, apply -XX:-UseBASE64Intrinsics as a temporary workaround.Table 1: Affected JDK distributions and versions.Hardware prerequisitesThe vulnerable assembly routine is only emitted by the HotSpot C2 JIT compiler on x86-64 processors that support AVX-512 VBMI (avx512f, avx512bw, avx512vbmi, bmi2):Vulnerable Intel server CPUs: Intel Xeon Ice Lake, Sapphire
[…]
Content was trimmed to protect the source. Please visit the original article for the full text.
This article has been indexed from Security Research | Blog
Related