Java4Shell Base64 bug can enable RCE in OpenJDK (CVE-2026-114938)
Original title: Java4Shell: A critical flaw with a narrow reach
Only OpenJDK 17.0.6 and later on x86-64 CPUs with AVX-512 VBMI are affected, and abuse is unreported.
Oracle and the OpenJDK project shipped fixes on November 17 for CVE-2026-114938, a memory-corruption bug in Java’s Base64 decoder that Calif named Java4Shell. A short malformed input can write 62 bytes past a buffer on a fast x86-64 decode path. Calif showed unauthenticated remote code execution on default Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, plus post-login execution on several other Java apps. CISA urged organizations to patch, and there are no reports of in-the-wild abuse.
Unconfirmed: Oracle and Calif publish different CVSS scores, and no fixed version strings are named.
- Oracle scores it 8.1 and calls it difficult to exploit; Calif scores it 9.2.
- ARM64 processors and Java Web Start or applets are not affected.
- Calif says each exploit chain is application-specific, with no universal exploit.
- Home users rarely expose a Java service that decodes Base64 from the internet.
Impact: Memory corruption and possible remote code execution
| Product | Affected |
|---|---|
| Oracle OpenJDK | from 17.0.6 onward |
- 1.Patch OpenJDK-based Java runtimes on x86-64 hosts that expose Base64-decoding services.
- CVEs
- CVE-2026-114938
- Vendors
- Oracle
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-114938 | Unauthenticated RCE in Oracle Java SE Compiler | 8.1 | <1% | PoC ×15 |
From the original article
2 min read at malwarebytes.com
Researchers used AI to find a Java vulnerability and named it Java4Shell. Here’s why organizations need to patch.
By @MetallicaMVP · malwarebytes.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.