Java4Shell
2 steps1 pieces5 Sources
Java4Shell (CVE-2026-114938) is a critical memory corruption vulnerability in OpenJDK's Base64 decoder, disclosed on November 17, 2026. The flaw resides in the AVX-512 VBMI optimized assembly code used on specific x86-64 processors (Intel Ice Lake and newer, AMD Zen 4 and newer). Malformed Base64 input can cause an out-of-bounds write of 62 or 63 bytes, potentially leading to remote code execution (RCE), heap disclosure (dubbed "JavaBleed"), or denial of service.
Security firm Calif.io reported that pre-authentication RCE was demonstrated against default configurations of Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate. Post-authentication RCE was shown in Kafka, Solr, Elasticsearch, Gerrit, and Spinnaker. However, experts from VulnCheck and Datadog Security Labs note that there is no universal exploit; achieving reliable RCE requires target-specific heap manipulation and bypassing ASLR, making widespread automated exploitation difficult compared to simple crashes.
Oracle assigned a CVSS 3.1 score of 8.1 (High), while Calif.io and Red Hat use CVSS 4.0 scores of 9.2 and 9.8 respectively, reflecting differing views on attack complexity. Patches were released by Oracle and several vendors on November 17. Interim mitigation involves starting JVMs with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 on affected x86-64 systems. ARM64 systems and older Java versions (8, 11) are not affected.
How it got here
November 17, 2026: Oracle and OpenJDK maintainers release security advisories and patches for CVE-2026-114938. Calif.io publicly discloses technical details and proof-of-concept exploits demonstrating pre-auth RCE in major enterprise applications.
phoronix.com ↗November 18, 2026: SecurityWeek and other outlets report conflicting severity assessments. While Calif.io claims easy RCE paths, VulnCheck notes that real-world RCE requires significant per-target effort. CISA urges immediate patching for internet-exposed systems.