Oracle has released fixes for Java4Shell, a memory-corruption vulnerability that researchers say they used to execute code on several enterprise applications without logging in.
Tracked as CVE-2026-114938, the flaw affects hardware-accelerated Base64 decoding in certain Java runtimes. Exposure depends on the Java build, processor and application, so running Java does not automatically make a server vulnerable.
Researchers at Calif assigned it a critical CVSS 4.0 score of 9.2. Oracle’s November security advisory separately rates it 8.1 under CVSS 3.1, with high attack complexity and no authentication or user interaction required. The scores use different versions of the assessment system.
A decoder error inside the Java runtime
Applications use Base64 to represent binary information as text, including in authentication messages and file transfers. On supported processors, OpenJDK speeds up decoding with specialised machine instructions.
According to Calif’s technical report, malformed input can cause that accelerated routine to write outside its allocated memory. Java subsequently rejects the input, but neighbouring memory may already have been corrupted.
Calif says it developed ways to turn the corruption into memory disclosure and remote code execution. Its comparison with Heartbleed concerns the ability to read sensitive memory, not an identical underlying bug.
During its testing, Calif reports achieving pre-authentication code execution against Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. It also reports post-authentication exploitation of Kafka Broker, Solr, Elasticsearch, Gerrit and Spinnaker.
Those are the researchers’ findings, not evidence that every installation of those products is exploitable. Calif says each application needs a tailored exploit and is withholding the product-specific chains while organisations update.
Check the processor as well as the Java version
Two servers running the same Java build can have different exposure because of their processors. Calif says the vulnerable decoder uses AVX-512 VBMI instructions on compatible x86-64 chips. ARM64 processors are unaffected.
Companies also need to check Java runtimes supplied inside applications and container images. Updating a separately installed system JDK does not establish that those bundled copies have changed.
The table below lists the Java versions affected by Java4Shell:
| Java branch | Affected versions |
|---|---|
| Java 17 | 17.0.6 through 17.0.21 |
| Java 21 | Through 21.0.13 |
| Java 25 | Through 25.0.5 |
| Java 27 | Through 27.0.1 |
| Java 8 Performance Pack | 8u511b33-perf |
Standard Java 8, Java 11 and Java 17.0.0 through 17.0.5 do not contain the vulnerable decoder described in the research. These exclusions concern Java4Shell specifically and do not mean older releases are safe from other vulnerabilities.
Oracle also lists affected GraalVM products in its advisory. Organisations using another OpenJDK distribution should obtain the corresponding fix from that supplier, since package names and release identifiers differ.
Researchers report code execution, with limits
Dom Glavach, chief information security officer at application security company Black Duck, said companies should act on the available fixes while keeping the reported exploit results in context.
“Oracle has confirmed the flaw and shipped fixes. The discoverers report they turned it into code execution against well-known enterprise products without logging in,” Glavach told Hackread.com.
He noted that the researchers are withholding those chains and that he said he had not seen independent confirmation of the product-specific exploits. Glavach also advised companies to prioritise internet-facing identity and build systems and avoid unverified fixes or purported exploits circulating online.
Apply the runtime update, then restart the application
Companies should obtain a patched Java runtime from their supplier, check which runtime each application actually launches and restart affected services after replacement. Applications with vendor-managed Java installations may require an application update or specific vendor instructions.
Where an update cannot be installed immediately, Calif recommends starting the runtime with -XX:-UseBASE64Intrinsics to disable the accelerated Base64 routines. It also lists -XX:UseAVX=2 as an alternative on x86-64 systems, while warning that this second option prevents OpenJDK from starting on ARM.
Administrators should test any temporary startup change with the application vendor. Disabling the vulnerable optimisation can reduce exposure while a patch is arranged, but companies still need to replace affected runtimes, including copies packaged inside applications and containers.
