A critical memory corruption vulnerability, dubbed Java4Shell and cataloged as CVE-2026-114938, has been identified within the Open Java Development Kit (OpenJDK). The flaw, which affects versions 17, 21, 25, and 27, was disclosed on November 17, 2026, by the California-based security firm Calif following reports of premature information leaks. While Oracle has assigned the vulnerability a high-severity score of 8.1 using the CVSS v3.1 framework, Calif has classified it as critical with a 9.2 score under CVSS v4.0.
The vulnerability stems from a memory corruption issue that can be triggered by a single malformed message. In scenarios involving unauthenticated attackers, this defect could potentially lead to remote code execution (RCE) across a wide array of Java-based applications. Confirmed services susceptible to such attacks include Atlassian products like Jira and Confluence, as well as Keycloak, JFrog Artifactory, Jenkins, and PingFederate. Additionally, various OpenJDK distributions are affected, including those from Amazon Corretto, Eclipse Temurin, Microsoft, Azul, BellSoft, SAP, Red Hat, and Oracle.
Other enterprise services, such as Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker, are also considered vulnerable, though exploitation in these instances requires the attacker to be authenticated. Despite the broad potential impact, security researchers from VulnCheck and Endor Labs have clarified that the flaw is not universally exploitable. The vulnerability is hardware-specific, relying on the presence of AVX-512 VBMI instructions within the server processor.
Technical analysis indicates that the defect exists in a specific decoding path utilized by certain Intel and AMD server processors. Systems lacking these specific instruction sets, such as ARM-based servers like AWS Graviton, are not impacted by the vulnerability. Researchers have successfully reproduced the issue on Intel Ice Lake hardware, confirming that processors without the relevant AVX-512 support utilize an alternative decoding path that remains unaffected. As of November 18, 2026, there have been no documented reports of the vulnerability being exploited in the wild.
In response to the disclosure, the US Cybersecurity and Infrastructure Security Agency (CISA) issued an emergency advisory on November 17, urging organizations to prioritize patching. While the maintainers of OpenJDK have released a fix, the timeline for deployment remains dependent on individual vendors shipping updated builds.
CISA has provided specific mitigation guidance for organizations unable to apply patches immediately. Recommended temporary measures include enforcing strict input-size limits, restricting unauthenticated access, and validating Base64 input at application boundaries. Organizations are also advised to conduct comprehensive reviews of their software inventories, as Java runtimes are frequently bundled within container images, appliances, and third-party applications, often remaining hidden from standard asset tracking.
Security teams are encouraged to monitor environments for indicators of compromise, such as unexpected Java Virtual Machine (JVM) crashes, the presence of rogue Java runtimes, or suspicious Java processes. Oracle has published official security advisories, and organizations are directed to follow vendor-specific guidance to ensure that internet-facing systems are secured as a priority.




