Java4Shell CVE-2026-114938: OpenJDK Base64 RCE Patch Guide
Java4Shell CVE-2026-114938 affects OpenJDK's x86-64 Base64 decoder. Check exposure, fixed runtimes, safe workarounds and live JVM verification.


On this page
On this page8 sections
On 17 November 2026, the Cybersecurity and Infrastructure Security Agency (CISA) urged immediate patching of Java4Shell. The Common Vulnerabilities and Exposures (CVE) entry CVE-2026-114938 covers a memory-corruption flaw in OpenJDK’s HotSpot Java Virtual Machine (JVM). Malformed Base64 can cause crashes, memory disclosure or Remote Code Execution (RCE) when the vulnerable decoding path executes.
Oracle assigns 8.1 under the Common Vulnerability Scoring System (CVSS) 3.1, with high attack complexity; Calif assigns 9.2 under CVSS 4.0. The scores use different systems and are not directly comparable.
What to Remember
- Scope: Unpatched Java 17 from 17.0.6, plus 21, 25 and 27; runtime presence alone does not prove exploitability.
- Hardware: x86-64 Advanced Vector Extensions 512 (AVX-512) with Vector Byte Manipulation Instructions (VBMI); ARM64 excluded.
- Fix: Oracle’s 17 November patches end in
.1; October’s 17.0.21 is not fixed. - Interim: Disable Base64 intrinsics, restart, then verify the live JVM flags.
How the OpenJDK Base64 Bug Works
java.util.Base64.Decoder reaches the native intrinsic through just-in-time (JIT) compilation. Invalid padding underflows the tail’s output length, enabling a full 64-byte store with largely fixed values. 62 or 63 bytes can escape the output buffer before IllegalArgumentException; catching the exception cannot undo corruption.
Exposure requires an unpatched runtime, all four processor features (avx512f, avx512bw, avx512vbmi, bmi2), and attacker-controlled input reaching the optimised decoder. Trace headers, tokens and uploads with my secure code review checklist.
Which Java Versions Are Fixed?
OpenJDK’s risk matrix identifies supported lines 17, 21, 25 and 27; Java 17’s vulnerable code starts at 17.0.6. Standard Java 8 and 11 are excluded, but Oracle’s Java 8 Enterprise Performance Pack 8u511b33-perf is affected.
The Java 8 Performance Pack fix is 8u513-perf. Oracle’s 17 November release notes confirm the following supported-line patches:
| Oracle Java line | Affected builds | First fixed runtime |
|---|---|---|
| 17 | 17.0.6 through 17.0.21.0.3 | 17.0.21.1 |
| 21 | Through 21.0.13.0.3 | 21.0.13.1 |
| 25 | Through 25.0.5.0.3 | 25.0.5.1 |
| 27 | Through 27.0.1.0.3 | 27.0.1.1 |
17.0.21 without .1 remains vulnerable. Temurin’s 18 November guidance lists fixed builds 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, and 27.0.1.1+4. Platform binaries and container images are being published as testing completes.
What Exploitation Has Been Demonstrated?
Calif reports laboratory unauthenticated RCE against Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Calif’s chains depend on input lengths, heap layout and network behaviour; no universal exploit exists.
Code execution inherits the Java service’s permissions, including access to application secrets.
Datadog independently reproduced memory corruption and crashes, not a universally portable RCE exploit. Calif’s public proof of concept (PoC) triggers corruption rather than remote takeover.
As of 18 November, Tenable reports GreyNoise exploitation attempts without confirmed successful sensor compromise. The cited reporting does not establish successful in-the-wild exploitation.
Patch, Restart and Verify Every Java Service
Inventory embedded runtimes and deployed containers, not just the shell’s java. As with PHP2Shell runtime patching and Node.js Brotli remediation, application-package updates cannot replace the vulnerable engine.
Install a vendor-confirmed fix, rebuild and redeploy images, and fully restart every Java service. Run read-only checks inside the target Linux environment; query the actual service process:
# Linux: all four processor flags are required
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' \
| grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
# Replace the placeholder with the service JVM process ID
JVM_PID='REPLACE_WITH_JVM_PID'
jcmd "$JVM_PID" VM.version
jcmd "$JVM_PID" VM.flags -all | grep -E 'UseBASE64Intrinsics|UseAVX'Use jcmd under the service account. Verify every replica and rollback image.
Temporary Workarounds and Detection
Add -XX:-UseBASE64Intrinsics to existing service startup options if patching must wait; restart and confirm UseBASE64Intrinsics = false. Alternatively, -XX:UseAVX=2 is x86-64-only, affects other acceleration, and can prevent ARM64 JVM startup.
Skip either workaround on unaffected ARM64 systems. Proxy buffering is not a universal fix.
Investigate hs_err_pid*.log, unexpected crashes, bursts of IllegalArgumentException and malformed Base64 tokens. Correlate request metadata without storing credentials or tokens; crash and validation signals are heuristics, not proof.
Conclusion: Verify the Running Runtime
Prioritise reachable internet-facing decoders, then close embedded-runtime and container blind spots. Patching is the fix; startup flags are temporary controls.
Record the running build and effective flags for every replica. A fixed file on disk is not a remediated service.
For runtime-security architecture support, contact me on LinkedIn or [email protected].
FAQ
Frequently Asked Questions (FAQ)
What is Java4Shell CVE-2026-114938?
Java4Shell corrupts heap memory in HotSpot’s optimised Base64 decoder. Reachable vulnerable deployments can suffer crashes, memory disclosure or RCE.
Are ARM64 and standard Java 8 or 11 affected?
Native ARM64 and standard Java 8 and 11 do not use the vulnerable path. Oracle Java 8 Enterprise Performance Pack 8u511b33-perf is an exception.
Which Oracle Java releases fix CVE-2026-114938?
Oracle released 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 on 17 November 2026. Replace the runtime and restart every Java service.
Can catching IllegalArgumentException prevent Java4Shell?
The out-of-bounds write occurs before the exception. Use a patched runtime or temporarily disable Base64 intrinsics and restart.
Is every Keycloak or Jenkins installation exploitable?
Runtime build, processor features and decoder reachability determine exposure. Calif’s RCE chains require target-specific heap and application conditions.
Resources
- CISA: 17 November patching alert
- Oracle: November 2026 security advisory
- OpenJDK: 17 November vulnerability advisory
- Calif: Java4Shell technical disclosure



