Java4Shell (CVE-2026-114938) Corrupts Memory; Calif Reports RCE in Products

· Original article ↗

Summary

A hardware-specific OpenJDK Base64 decoder flaw can overwrite 62 bytes beyond a buffer. Calif reports product-specific RCE, but no in-the-wild exploitation was reported as of Nov. 18. The article details affected versions, fixes, workarounds and detection.

Key points

  • On supported x86-64 processors, the OpenJDK Base64 decoder can mishandle malformed input ending in “=” and overwrite 62 bytes beyond an allocated buffer before rejecting it.
  • Calif reports achieving remote code execution in several products, including Jira, Confluence, Jenkins and Keycloak; the article says exploitation depends on each target's heap layout and timing.
  • The flaw requires an x86-64 processor with AVX-512 VBMI support; ARM64 is not affected. Exposure can vary between hosts running the same container image.
  • As of Nov. 18, no in-the-wild exploitation had been reported. Calif had published a memory-corruption reproducer but withheld product-specific exploit chains.
  • The article lists Oracle fixed builds for affected Java versions and advises applying vendor fixes, then restarting applications and rebuilding or redeploying containers.
  • If patching is not immediately possible, researchers recommend testing the JVM option -XX:-UseBASE64Intrinsics to disable the vulnerable code path; Oracle and OpenJDK had not published an official workaround.
  • Suggested hunting includes malformed Base64 values, bursts of decoder exceptions or JVM crashes, and unexpected child processes, outbound connections or new files. The article says no IOCs had been published.

Article Details

Vulnerability Types
  • Memory corruption
  • Out-of-bounds write
Severity
Critical; CVSS 4.0 score 9.2
Affected Versions
  • OpenJDK 17.0.6 or newer
  • Oracle Java SE 17.0.6–17.0.21 (fixed in 17.0.21.1)
  • Oracle Java SE 21 up to 21.0.13 (fixed in 21.0.13.1)
  • Oracle Java SE 25 up to 25.0.5 (fixed in 25.0.5.1)
  • Oracle Java SE 27 up to 27.0.1 (fixed in 27.0.1.1)
  • Oracle Java SE 8u511b33-perf
Exploitation Status
not_reported
Exploit Availability
public_poc
Patch Status
partial
Workarounds
  • Start the JVM with -XX:-UseBASE64Intrinsics to disable the vulnerable code path; researchers recommend testing it before deployment.

CVE

Vendors

Products

Apache Kafka BrokerWith authentication: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and SpinnakerApache SolrWith authentication: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and SpinnakerApache StrutsSample applications built on Apache Struts and Spring Boot, plus a client-side exploit against a Java client that connects to a malicious TLS serverAtlassian JiraWithout authentication: Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederateConfluenceWithout authentication: Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederateElasticsearchWith authentication: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and SpinnakerGerritWith authentication: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and SpinnakerJenkinsWithout authentication: Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederateJFrog ArtifactoryWithout authentication: Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederateKeycloakWithout authentication: Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederateOpenJDKSpecifically, there's a memory corruption bug in OpenJDK's Base64 decoder.PingFederateWithout authentication: Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederateSpinnakerWith authentication: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and SpinnakerSpring BootSample applications built on Apache Struts and Spring Boot, plus a client-side exploit against a Java client that connects to a malicious TLS server

Related Articles