CybersecurityVulnerabilities & Patches
Java4Shell: critical OpenJDK flaw patched by Oracle in November update
Researchers disclosed a high-severity memory corruption bug in OpenJDK's Base64 decoding that can allow remote code execution in widely used enterprise software. Oracle released a fix on 17 November, and admins are urged to update or apply workarounds.

Key takeaways
- CVE-2026-114938, dubbed Java4Shell, is a memory corruption bug in OpenJDK's Base64 decoding, scored 8.1 by NVD and 9.2 by Calif.
- OpenJDK 17.0.6 and later are affected, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.
- Researchers confirmed exploitable versions of Jenkins, Atlassian Jira, Confluence, Keycloak and other enterprise applications, some without authentication.
- Oracle patched the flaw on 17 November 2026; unpatched systems can use -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 as temporary mitigations.
In this article
What researchers found
A critical security flaw in the Java runtime has been disclosed, and Oracle has already shipped a fix. According to TechRadar, researcher Quang Long from Calif found the bug in OpenJDK, the open-source implementation of the Java platform, and named it Java4Shell. The issue is tracked as CVE-2026-114938.
The National Vulnerability Database scores it 8.1 out of 10, which is high, while Calif rates it 9.2 out of 10, or critical. The flaw is a memory corruption bug, meaning software writes to areas of memory it should not touch. That can let attackers read sensitive data or run their own code on a vulnerable system.
The affected component is Base64, a decoding function that converts binary data such as images or files into text so it can be transmitted or stored more easily. TechRadar reports the bug only affects hardware-accelerated decoding on some x86-64 processors that support AVX-512 instructions.
Which software is affected
OpenJDK versions 17.0.6 and later are affected, along with every Java distribution built from that code.
Applications running on these distributions may also be exposed. Researchers confirmed vulnerabilities in some versions of Jenkins, Atlassian Jira, Atlassian Confluence and Keycloak, and the list is not exhaustive.
In testing, the researcher achieved unauthenticated remote code execution, meaning no login was needed, on Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. On Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker, the exploit required authentication.
The exploit is surprisingly simple. Calif triggered the bug with 64 letter A characters followed by an equals sign, and older OpenJDK 17 versions needed 128 characters. There is no universal exploit, though, so attackers must adapt their approach for each individual application.
How the bug was found
TechRadar reports that Long was inspired by the earlier PHP2Shell discovery and used OpenAI's Codex AI coding assistant to locate the bug. The search reportedly took about an hour and around $200 in tokens. AI agents also helped build exploitation chains tailored to specific applications.
Long stressed the scale of what is at stake. Java is the third most popular programming language and powers a large share of major companies. Banking, aviation, telecommunications and other critical sectors rely on it, so a flaw in the runtime can ripple across many industries.
Patches and workarounds

Oracle fixed CVE-2026-114938 on 17 November 2026 as part of its November Critical Security Patch Update. Organisations should install that update as soon as possible.
Systems that cannot be patched straight away have temporary options, according to TechRadar. Admins can disable hardware-accelerated Base64 decoding by starting OpenJDK with the -XX:-UseBASE64Intrinsics option. On x86-64 systems, the -XX:UseAVX=2 option disables AVX-512 instructions.
These measures are workarounds only, not permanent fixes. Since the flaw can lead to data theft or remote code execution, updating remains the only real solution.
Sources
Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.



