Java4Shell flaw can enable remote code execution under narrow conditions

· Original article ↗

Summary

CVE-2026-114938 affects OpenJDK’s x86-64 Base64 decoder and can enable application-specific remote code execution when several conditions align. Oracle and OpenJDK released fixes; no in-the-wild abuse was reported.

Key points

  • Oracle and OpenJDK released fixes on November 17 for the memory-corruption flaw, named Java4Shell by Calif.
  • Malformed input can cause the decoder’s x86-64 fast path to write 62 bytes past a memory buffer.
  • The flaw affects OpenJDK 17.0.6 and later on x86-64 processors supporting AVX-512 VBMI; ARM64 chips are not affected.
  • Remote code execution requires an exposed application that decodes crafted input and a target-specific exploit chain; Calif says there is no universal exploit.
  • Calif demonstrated unauthenticated RCE on default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate, and post-login RCE on several other applications.
  • The article reports no known in-the-wild exploitation and says CISA urged organizations to patch promptly.

Article Details

Vulnerability Types
  • Memory corruption
  • Out-of-bounds write
Severity
Oracle rates CVE-2026-114938 8.1 under CVSS 3.1 and describes it as difficult to exploit; Calif rates it 9.2 (Critical) under CVSS 4.0.
Affected Versions
  • OpenJDK 17.0.6 and later, including distributions built on it
Exploitation Status
not_reported
Exploit Availability
unknown
Patch Status
available

MITRE ATT&CK

CVE

Vendors

Products

Apache SolrArtifactory, Jenkins and PingFederate. It also demonstrated post-login code execution on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.Atlassian JiraA critical-sounding Java flaw is making headlines. Most consumers are unlikely to be affected, but companies running Jira, Confluence, Jenkins and similar tools have work to do.ConfluenceA critical-sounding Java flaw is making headlines. Most consumers are unlikely to be affected, but companies running Jira, Confluence, Jenkins and similar tools have work to do.ElasticsearchArtifactory, Jenkins and PingFederate. It also demonstrated post-login code execution on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.GerritJenkins and PingFederate. It also demonstrated post-login code execution on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.JavaExploitation depends on the Java runtime, processor and applicationJenkinsA critical-sounding Java flaw is making headlines. Most consumers are unlikely to be affected, but companies running Jira, Confluence, Jenkins and similar tools have work to do.JFrog Artifactoryremote code execution without logging in on default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. It also demonstrated post-login code execution on Kafka, Solr,KafkaConfluence, Artifactory, Jenkins and PingFederate. It also demonstrated post-login code execution on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.Keycloakin the wild. Calif demonstrated remote code execution without logging in on default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. It also demonstrated post-login code executionOpenJDKOn November 17, Oracle and the OpenJDK project shipped fixes for CVE-2026-114938, a memory-corruption bug in Java’s Base64 decoder. Security firm Calif discovered the flaw and named it Java4Shell. CISA urgedPingFederatewithout logging in on default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. It also demonstrated post-login code execution on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.SpinnakerPingFederate. It also demonstrated post-login code execution on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.

Related Articles