Skip to content
Java4Shell: OpenJDK Base64 decoder memory corruption (CVE-2026-114938) enables RCE

Java4Shell: OpenJDK Base64 decoder memory corruption (CVE-2026-114938) enables RCE

First seen 22 Nov 2026, 16:14 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 22, 2026 at 16:15 UTC
  • •CVE-2026-114938 is a memory-corruption bug in the AVX-512 VBMI Base64 decoder intrinsic in OpenJDK 17.0.6 and newer on x86-64.
  • •Vendor patches are available: OpenJDK published an advisory and Oracle shipped fixes in its November 2026 Critical Patch Update.
  • •Only x86-64 CPUs with AVX-512 VBMI are reported affected; ARM64 is stated not to be affected.
  • •Reported RCE demonstrations against Keycloak, Jira, Confluence and others come from a single source and are not independently confirmed.
  • •Stopgaps include Cloudflare WAF rules (logging by default) and JVM startup flags that disable the accelerated decoder; inventory all Java runtimes.

CVE-2026-114938, dubbed Java4Shell, is a memory-corruption flaw in the hand-written AVX-512 VBMI assembly used by the Base64 decoder in OpenJDK 17.0.6 and newer on x86-64 processors. Per the articles, a malformed input (128 'A' characters followed by '=') causes a negative output length, producing a masked store that writes 62 bytes past the end of the array. Calif disclosed the issue on 17 November 2026; the Dev.To article reports a CVSS 4.0 score of 9.2, while the KNOWN CVE DATES record lists CVSS 8.1. OpenJDK published an advisory and Oracle shipped patched builds in its November 2026 Patch Update. The Dev.To article attributes to Calif demonstrations of pre-authentication remote code execution against Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and post-authentication execution against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker; these claims come from that single article and were not independently verified in the other sources. Affected builds reportedly include Corretto, Temurin, Zulu, Microsoft, Red Hat, SapMachine, Liberica and Oracle builds; Calif states ARM64 CPUs are not affected. Cloudflare reportedly added six managed WAF rules that log matching requests by default, and two JVM flags are described as a stopgap. Lemire's analysis confirms the mechanism in detail and notes he has not checked the RCE claims.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-17
Calif discloses CVE-2026-114938
Disclosed as Java4Shell; the Dev.To article reports CVSS 4.0 of 9.2, while the record lists CVSS 8.1.
Dev.To
2026-11-17
OpenJDK advisory and Oracle patches released
OpenJDK published its advisory and Oracle shipped patched builds in its November 2026 Critical Patch Update at 21:00 UTC.
Dev.To
2026-11-18
First public PoC
Lemire published a detailed root-cause analysis of the out-of-bounds write.
Lemire.Me

More articles in this cluster (3)

Following this threat?

Track Calif and CVE-2026-114938 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Am I affected?
You are potentially affected if you run OpenJDK 17.0.6 or newer on an x86-64 CPU with AVX-512 VBMI; the articles state ARM64 is not affected. Check every Java runtime, including those bundled in application images.
How urgent is this?
Oracle and OpenJDK have released patched builds, so applying the November 2026 update is the primary remedy. Sources report a CVSS of 8.1 in the record and 9.2 in one article.
What should we do first?
Inventory all Java runtimes and apply the patched builds from your vendor. If patching must wait, deploy the Cloudflare WAF rules or the documented JVM flags as a temporary measure.