On November 17, 2026, security firm Calif disclosed Java4Shell, tracked as CVE-2026-114938. The flaw sits inside OpenJDK's hardware-accelerated Base64 decoder and can corrupt server memory when fed specially crafted input. Oracle shipped emergency patches on the same day as part of its November 2026 Critical Patch Update. South Korea's KISA issued a security advisory the following day, November 18 (KISA Advisory 72313). Calif rates the severity at CVSS 4.0 score 9.2 (Critical).
What is Java4Shell in plain terms?
Java is the language powering most enterprise servers, web backends, and financial systems. Base64 is the encoding format used to pass binary data — login tokens, file uploads, API payloads — as plain text across the network. Almost every Java web service processes Base64 somewhere.
Java4Shell is a bug in the code that decodes Base64. Modern Intel and AMD CPUs include an instruction set called AVX-512, which Java uses to speed up that decoding. The bug lives in that fast path: a specially padded Base64 string — Calif's proof-of-concept uses 64 "A" characters followed by "=" — triggers an out-of-bounds write in the JVM process's memory. In the worst case, an attacker who can send that input to a vulnerable server may be able to execute arbitrary code on it. Some researchers note that reliable remote code execution has not been independently confirmed and that a crash is the more predictable outcome, so the full impact depends on the target application and server configuration.
Who is at risk?
Server operators and developers running Java-based applications are the primary audience for this advisory. The flaw requires an attacker to deliver crafted Base64 input to a running Java process, so it only matters where untrusted input can reach the decoder. Calif tested against the following software and found it vulnerable:
- No authentication required: Keycloak, Atlassian Jira, Atlassian Confluence, Jenkins, JFrog Artifactory, PingFederate
- Authentication required: Apache Kafka, Elasticsearch, Apache Solr, Gerrit, Spinnaker
If you operate any of those products on an x86-64 server with AVX-512 support, treat this as urgent. Calif says it did not publish a weaponized exploit, but the vulnerability details are now public and exploitation attempts will likely follow.
Are regular PC users at risk?
Not directly. Desktop Java runtimes that only run local applications do not expose the Base64 decoder to external attackers. The attack requires sending malicious input to a live Java service. That said, Oracle recommends that all Java SE users apply the update regardless, and there is no cost to patching a desktop runtime.
Affected versions and patched versions
Based on Oracle's November 2026 Critical Patch Update and the KISA advisory:
| Product | Vulnerable builds (examples) | Fixed version |
|---|---|---|
| Oracle Java SE 8 | 8u511b33-perf | 8u513 (1.8.0_513-b04) |
| Oracle Java SE 17 | 17.0.21.0.3 (OpenJDK 17.0.6+) | 17.0.21.1 |
| Oracle Java SE 21 | 21.0.13.0.3 | 21.0.13.1 |
| Oracle Java SE 25 | 25.0.5.0.3 | 25.0.5.1 |
| Oracle Java SE 27 | 27.0.1.0.3 | 27.0.1.1 |
| GraalVM for JDK 17/21 | 17.0.21.0.3 / 21.0.13.0.3 | 17.0.21.1 / 21.0.13.1 |
If you run an OpenJDK-based distribution — Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat OpenJDK — check your vendor's release channel for the corresponding patched build.
Action checklist
- ✅ Check your Java version:
java -version - ✅ Update to the patched version listed above (highest priority)
- ✅ If an immediate update is not possible, add
-XX:-UseBASE64Intrinsicsto your JVM startup flags as a temporary mitigation (disables the AVX-512 fast path) - ✅ Prioritize internet-facing Keycloak, Jira, Confluence, and Jenkins instances
- ✅ Review firewall and WAF rules to monitor for unusual Base64 payloads
- ✅ Verify application behavior after patching
Note: Oracle has not officially confirmed -XX:-UseBASE64Intrinsics as a supported workaround. Applying the patch is the definitive fix.
South Korea's KISA advisory
KISA (Korea Internet and Security Agency) published Security Advisory 72313 on November 18, 2026, covering CVE-2026-114938 and five related Oracle Java SE CVEs from the same Critical Patch Update. KISA urges all organizations running Oracle Java SE or GraalVM to apply Oracle's November 2026 patch. For security inquiries, contact KISA's cybersecurity center at 118.
Explore KOAT Apps
Investing insights, fitness tracking, English vocabulary — all in one place.