Cisco Talos is tracking the disclosure of a critical vulnerability in OpenJDK Java (CVE-2026-114938), dubbed “Java4Shell,” with a CVSS 4.0 score of 9.2 that may lead to unauthenticated remote code execution (RCE). This vulnerability can be triggered by sending a malformed Base64 input to affected JVMs, which can result in RCE.

Details

This vulnerability affects OpenJDK Java versions 17.0.6 and later running on x86-64 CPUs with AVX-512 VBMI (Vector Byte Manipulation Instructions) support enabled. These vulnerabilities have already been tested against a suite of Java applications with success, but the attack surface is likely much larger as additional targets are tested and confirmed.

This vulnerability does require a specific subset of processors that support AVX-512 VBMI; these include commonly deployed processors from both Intel and AMD, resulting in a large potential attack surface of vulnerable systems, including both on-premise and cloud environments.

Cisco Talos would like to thank Calif.io for sharing the details of the vulnerability in advance of public disclosure.

Observed exploitation

Talos has not observed in-the-wild exploitation of this vulnerability yet. However, we anticipate probing attempts may pick up soon after public disclosure. Talos will continue to monitor for exploitation attempts and will provide updates accordingly.

Recommendations and guidance

Talos recommends applying the software update for this vulnerability. If immediate patching is not possible, other mitigations can be implemented in the interim. The primary mitigation is starting the JVM with AVX-512 support disabled. This can be done by starting the application with “=XX:UseAVX=2”. Note that this is only applicable for x86-64 systems, as ARM-based processors will not recognize the command, likely resulting in failure to start.

Cisco is following its well-established process to evaluate its products and will provide updates shortly. Customers should reach out to their sales teams with specific questions

Coverage

SNORT® SIDs covering this vulnerability for subscribers:

Snort2: 1:67502 - 1:67513

Snort3: 1:301754, 1:67502 - 1:67513

These rules detect malformed base64 data in specific HTTP request fields associated with the vulnerability. This vulnerability is implementation specific. Talos made every effort to identify as many common vulnerable applications as possible and cover potential attack vectors in those applications.

Splunk customers can refer to Splunk’s ES Content Updates (ESCU) pre-packaged security content for detections against high-profile vulnerabilities. Existing detections from Splunk cover suspicious indicators such as heavily encoded content, and post-exploitation scenarios such as arbitrary command execution or processes and web or application servers spawning shells.

Integrated Coverage