637/69 Thursday, November 19, 2026

Security researchers from Calif have disclosed a critical vulnerability in the OpenJDK runtime, dubbed Java4Shell and tracked as CVE-2026-114938, with a CVSS 4.0 severity score of 9.2. The vulnerability could allow unauthenticated attackers to execute arbitrary commands in Java applications widely deployed across enterprise environments worldwide. Affected versions include Java 17 versions 17.0.6 through 17.0.21, Java 21 up to version 21.0.13, Java 25 up to version 25.0.5, Java 27 up to version 27.0.1, and Java 8 Performance Pack version 8u511b33-perf. Meanwhile, Java 11 and Java 17 versions 17.0.0 through 17.0.5 are not affected.
The vulnerability, discovered with the assistance of artificial intelligence (AI), stems from a memory management flaw in native machine code that utilizes the AVX-512 VBMI CPU instruction set on x86-64 architecture to accelerate Base64 decoding. When the system processes specially crafted input containing improperly positioned equal signs (=), an out-of-bounds write may occur, overwriting adjacent memory locations. This could allow attackers to extract sensitive information or execute malicious commands through common application functionalities, such as authentication mechanisms and file uploads. The research team demonstrated unauthenticated exploitation against several widely used enterprise applications, including Keycloak, Atlassian Jira, Confluence, JFrog Artifactory, Jenkins, and PingFederate. They also demonstrated post-authentication exploitation in Apache Kafka Broker, Solr, Elasticsearch, Gerrit, and Spinnaker, as well as potential exploitation involving Apache Struts, Spring Boot, and client applications establishing TLS connections to malicious servers. However, the researchers have delayed the release of product-specific exploit code to give organizations additional time to secure their systems.
OpenJDK has issued a security advisory, and Oracle has released official security patches to address the vulnerability. System administrators are strongly advised to conduct a comprehensive inventory of servers and JDK distributions embedded within applications and containers, prioritizing patch deployment for internet-facing systems, identity management platforms, and build environments. If immediate patching is not possible, organizations can temporarily mitigate the risk by configuring the OpenJDK startup parameter -XX:-UseBASE64Intrinsics to disable hardware-accelerated Base64 decoding. Alternatively, the -XX:UseAVX=2 parameter may be used on x86-64 systems only, as it is not supported on ARM architectures and may prevent applications from starting. Organizations should also exercise caution when downloading or deploying patches and proof-of-concept code from unverified sources.
