Skip to content
NewA calmer, faster ZeroHour

OpenJDK Base64 flaw Java4Shell can yield code execution (CVE-2026-114938)

Original title: Java4Shell OpenJDK flaw: Exploitation is tricky and hinges on specific CPUs (CVE-2026-114938)

Help Net Securityby Zeljka Zorz ()3 min read
Part of a story covered by 21 sourcesOracle patches Java4Shell OpenJDK Base64 RCE (CVE-2026-114938)Merged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

The bug hits only x86-64 CPUs with AVX-512 VBMI; crashing a JVM is easy, but code execution needs extra leaks.

CVE-2026-114938 is a memory-corruption bug in OpenJDK’s Base64 decoder that can disclose memory or lead to remote code execution when applications decode attacker-controlled Base64. Oracle and the OpenJDK project fixed it on Tuesday, and CISA urges organizations to patch. Calif says it achieved unauthenticated code execution in default Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate, but only on CPUs with AVX-512 VBMI. There is no evidence of successful attacks.

Unconfirmed: No successful attacks are known; Calif and Oracle disagree on severity, and earlier affected versions are only described as likely.

Key facts
  • A trigger is 64 A characters plus one equals sign; older OpenJDK 17 needs 128.
  • Oracle scored the flaw 8.1; Calif scored it 9.2 under CVSS 4.0.
  • ARM64 CPUs are not affected, VulnCheck and Calif said.
  • Calif published a corruption-check proof of concept and withheld product exploit chains.
  • Authenticated code execution was shown in Kafka, Solr, Elasticsearch, Gerrit, and Spinnaker.
Security assessment · AI, from the articlePublic proof of concept

Impact: Memory disclosure or remote code execution via Base64 input

ProductAffected
Oracle Java SE8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3 (and likely earlier)
Oracle GraalVM for JDK17.0.21.0.3 and 21.0.13.0.3
Oracle GraalVM Enterprise Edition21.3.20.0.3
OpenJDKVulnerable builds used by named Java distributions
What to do
  1. 1.Inventory JDKs and Java runtimes and apply vendor patches when available.
  2. 2.If patching is delayed, validate Base64 input, limit size, and restrict unauthenticated access.
  3. 3.Monitor for unexpected JVM crashes, rogue runtimes, and suspicious Java processes.
Analyze CVE-2026-114938 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-114938
Unauthenticated RCE in Oracle Java SE Compiler
8.1<1%PoC ×15

From the original article

3 min read at helpnetsecurity.com

CVE-2026-114938, a memory corruption flaw in Open Java Development Kit’s Base64 decoder, can allow unauthenticated attackers to run code on servers hosting widely used Java applications. Nicknamed “Java4Shell” by Calif, the company whose researchers found it, CVE-2026-114938 was fixed by Oracle and the OpenJDK project on Tuesday.

Help Net Security

By Zeljka Zorz · helpnetsecurity.com

Read the full article at Help Net Security

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.