この記事では
- Java4Shell can cause memory corruption and, in some applications, remote code execution
- Exploitation depends on the Java runtime, processor and application
- Most home users are unlikely to be affected, but organizations should patch promptly
A critical-sounding Java flaw is making headlines. Most consumers are unlikely to be affected, but companies running Jira, Confluence, Jenkins and similar tools have work to do.
On November 17, Oracle and the OpenJDK project shipped fixes for CVE-2026-114938, a memory-corruption bug in Java’s Base64 decoder. Security firm Calif discovered the flaw and named it Java4Shell. CISA urged organizations to patch immediately.
After a run of high-profile computer problems and security scares, it’s understandable that another vulnerability with a catchy name would set alarm bells ringing. But it’s important to separate the potential damage from the likelihood of being affected. This is a serious issue for organizations running vulnerable applications, not a reason for every home user to assume their computer is at risk.
It doesn’t help that organizations give out different CVSS scores for the same vulnerability.
- Oracle rates it 8.1 under CVSS 3.1 and describes it as “difficult to exploit.”
- Calif rates it 9.2 (Critical) under CVSS 4.0.
Meanwhile, there are currently no reports of abuse in the wild. Calif demonstrated remote code execution without logging in on default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. It also demonstrated post-login code execution on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.
技術的な詳細
Base64 is a common way of representing binary data as text. It’s used in login protocols, file uploads and network messages. To decode it faster, OpenJDK uses special x86-64 CPU instructions.
The bug is in hand-written assembly code for that fast path. A short, malformed input can write 62 bytes past the end of a memory buffer.
For remote code execution, several conditions have to line up:
- The right processor. The flaw only affects x86-64 CPUs that support the AVX-512 VBMI instruction set. Examples include Intel Xeon from Ice Lake onward and AMD Zen 4 or newer. ARM64 chips aren’t affected.
- A recent OpenJDK-based Java. The flaw affects OpenJDK from 17.0.6 onward, and the distributions built on it.
- An exposed Java service. The attacker has to feed crafted data to a Java application that decodes it. Oracle notes it can only be exploited by supplying data to the affected APIs, such as through a web service. It can’t be exploited through untrusted Java Web Start applications or applets.
- A target-specific exploit. Calif says there is no universal exploit. Each chain needs a decoder route, a feedback path, a heap layout, and an application-specific action. The attack also works best with low, stable network latency, and Calif rented a VM in the same region as its target.
An ordinary home PC rarely runs a Java server that accepts Base64 input from the internet. Organizations running affected Java applications on vulnerable processors should patch promptly, since attackers may find narrow, application-specific paths to remote code execution.





