VYPR
patchPublished Nov 18, 2026· Updated Nov 21, 2026· 8 sources

Critical OpenJDK Vulnerability 'Java4Shell' Disclosed, Posing RCE Risk

Cisco Talos has identified 'Java4Shell' (CVE-2026-114938), a critical vulnerability in OpenJDK that allows unauthenticated remote code execution.

Cisco Talos is tracking a newly disclosed critical vulnerability in the Java Development Kit (JDK) known as "Java4Shell" (CVE-2026-114938). This flaw carries a CVSS 4.0 score of 9.2, indicating a severe security risk. The vulnerability allows unauthenticated remote code execution (RCE) by exploiting a specific weakness in how affected Java Virtual Machines (JVMs) handle malformed Base64 input.

The technical details reveal that the vulnerability impacts OpenJDK versions 17.0.6 and later. Crucially, exploitation requires the target system to be running on x86-64 CPUs that support AVX-512 VBMI instructions. This specific hardware requirement, however, still encompasses a significant number of commonly deployed servers and workstations from both Intel and AMD, presenting a broad potential attack surface across on-premise and cloud environments.

While Cisco Talos has not yet observed any exploitation attempts in the wild, the vulnerability has been successfully tested against a range of Java applications. This proof-of-concept testing indicates that attackers could potentially leverage this flaw to gain control of vulnerable systems once they identify suitable targets. The public disclosure of this vulnerability is likely to spur increased scanning and exploitation attempts in the near future.

To mitigate this threat, organizations are strongly advised to apply the latest software updates released for OpenJDK. For environments where immediate patching is not feasible, a temporary workaround exists: administrators can start the JVM with AVX-512 support disabled by using the command-line argument -XX:UseAVX=2. It is important to note that this mitigation is specific to x86-64 architectures; ARM-based processors will not recognize this command and may fail to start.

Beyond patching and configuration changes, security teams can enhance their defenses by deploying the Snort rules and Splunk detections recommended in the Cisco Talos advisory. These tools are designed to help detect the malformed Base64 data indicative of an attack attempt and identify suspicious post-exploitation activities on the network.

The disclosure of Java4Shell comes amidst a busy news cycle for cybersecurity, with other significant events including supply chain attacks targeting major websites via Optimizely, new RCE vulnerabilities in NGINX, and ongoing discussions around post-quantum cryptography. The constant stream of vulnerabilities underscores the persistent challenge organizations face in maintaining a secure posture against evolving threats.

Cisco Talos will continue to monitor for any signs of exploitation and will provide further updates as more information becomes available. The proactive identification and reporting of such critical vulnerabilities are essential for enabling the cybersecurity community to defend against potential widespread attacks.

Exploitation attempts for the Java4Shell vulnerability (CVE-2026-114938) have begun in the wild, with threat intelligence firms like GreyNoise and WatchTowr observing active scanning and probing. While initial attempts may not be fully functional, attackers are iterating on exploit chains, and some vendors like Atlassian and Jenkins are providing workarounds as patches continue to roll out across affected products from Cisco, Red Hat, and Siemens.

Palo Alto Networks has confirmed that CVE-2026-114938, a critical Java vulnerability previously discussed as 'Java4Shell', affects its Privilege Threat Analytics, Remote Access Connector, and on-premises HTML5 Gateway products. The vulnerability, an out-of-bounds write in the HotSpot JVM's Base64 decoder, requires specific hardware and software conditions for exploitation, including AVX-512 VBMI support and an enabled accelerated Base64 decoder. Palo Alto Networks has released specific version updates for its affected products, with no known workarounds for some, and is continuing to review its broader product portfolio.

This new report provides further technical details on the Java4Shell vulnerability (CVE-2026-114938), explaining that the flaw stems from an issue in OpenJDK's optimized Base64 decoding routine which uses specialized x86-64 CPU instructions. Specifically, malformed input can overwrite neighboring memory due to an incorrect calculation of the output length, potentially leading to sensitive memory disclosure or remote code execution.

This new article provides further detail on the hardware-specific nature of the Java4Shell vulnerability, noting that exploitation is dependent on the Java version, server processor, and application. Specifically, it highlights that CPUs supporting AVX-512 VBMI instructions are affected, while ARM-based servers like AWS Graviton are not, and that recent Intel and AMD server chips are among the vulnerable processors. As of the article's publication, no in-the-wild exploitation had been reported.

This Fortinet advisory provides specific details on affected versions of Oracle Java SE, GraalVM for JDK, and GraalVM Enterprise Edition, including version numbers such as 8u511b33-perf and 17.0.21.0.3. It clarifies that exploitation requires supplying data to specific APIs, rather than through untrusted Java Web Start applications or applets, and notes the vulnerability is difficult to exploit but can lead to a full takeover.

This new report from The Register highlights that the United States Cybersecurity and Infrastructure Security Agency (CISA) has urged immediate patching of CVE-2026-114938, a critical Java vulnerability dubbed "Java4Shell." The article also notes that the vulnerability's discovery by Calif.io may have been leaked prior to public disclosure, with the firm testing it against several prominent applications including Keycloak, Jira, Confluence, and Jenkins.

This update from Cisco Talos provides additional details on the Java4Shell vulnerability (CVE-2026-114938), including specific mitigation steps. Organizations can disable AVX-512 support by starting the JVM with the flag "=XX:UseAVX=2", though this is only applicable to x86-64 systems. Cisco has also released a security advisory detailing potentially affected products.

Synthesized by Vypr AI