Java4Shell Exploitation Attempts Emerge as Vendors Issue Advisories

Summary
CVE-2026-114938 affects certain OpenJDK builds on x86-64 CPUs with AVX-512 VBMI. Vendors report varying product impacts and are issuing fixes; observed probing has not established successful compromises.
Key points
- Java4Shell is a memory corruption flaw in OpenJDK Base64 handling, tracked as CVE-2026-114938. Exploitation requires an x86-64 CPU supporting AVX-512 VBMI; ARM systems are not affected.
- GreyNoise recorded more than 150 requests matching Java4Shell attacks from five IP addresses by early November 19, but saw no successful intrusions on its sensors. Other firms reported probing and exploitation attempts, without confirming compromise.
- Calif said it achieved unauthenticated RCE in default configurations of several enterprise applications, but each requires a tailored attack chain. Its released PoC triggers memory corruption; separate full or working RCE exploits were reported by VulnCheck and Immersive.
- Cisco confirmed more than a dozen affected products but had not released fixes and said no workarounds were available; it was still investigating IOS XE and UCS Central.
- Siemens recommends taking affected Industrial Edge Management instances offline while it prepares patches. Elastic reported product-specific requirements and impacts, including unauthenticated DoS in affected Logstash configurations.
- Keycloak released updated container images with a patched Java runtime. Jenkins advises updating Java and restarting controllers; Atlassian recommends disabling AVX-512 support for certain Data Center products until patches are available.
- Oracle, OpenJDK, Amazon, Microsoft, and Azul released patched builds or distributions; Red Hat said patches were being fast-tracked.
Article Details
- Vulnerability Types
- Memory corruption in OpenJDK's handling of Base64 data
- Severity
- Critical (Red Hat rating)
- Affected Versions
- OpenJDK 17.0.6 and newer
- RHEL 8
- RHEL 9
- RHEL 10
- Elasticsearch 7.17.3 and later
- Logstash 8.6.2 and later
- Keycloak container images 26.8.2-1 and 26.8.2-2
- Exploitation Status
- active
- Exploit Availability
- public_poc
- Patch Status
- partial
- Workarounds
- Siemens recommends taking affected Industrial Edge Management instances offline while patches are in progress.
- For the latest versions of Bamboo, Bitbucket, Confluence, Crowd, Jira, and Jira Service Management Data Center in standard installations, Atlassian recommends disabling AVX-512 support until patches are available.
MITRE ATT&CK
T1190 · Exploit Public-Facing ApplicationJava4Shell attempts targeted enterprise applications; Calif reported achieving unauthenticated remote code execution against default configurations of several applications.T1499.004 · Application or System ExploitationElastic reported that unauthenticated exploitation can trigger a denial-of-service condition in Elasticsearch.T1595.002 · Vulnerability ScanningReported scanners probed systems with requests matching the Java4Shell attack and correctly shaped exploit triggers.
CVE
People
Vendors
AmazonAmong Java distributors, Amazon, Microsoft, and Azul have released patched builds of their OpenJDK distributions.AtlassianAtlassian says it is working to address the issue in its cloud products, and that cloud customers do not need to take any action.AzulAmong Java distributors, Amazon, Microsoft, and Azul have released patched builds of their OpenJDK distributions.CiscoCisco’s product security team says it is aware of proof-of-concept (PoC) exploit code but has no knowledge of malicious use.ElasticAccording to Elastic, every Elasticsearch release from 7.17.3 onward is affected.MicrosoftAmong Java distributors, Amazon, Microsoft, and Azul have released patched builds of their OpenJDK distributions.OracleCalif disclosed the bug on November 17, the same day Oracle and the OpenJDK project released patches.Red HatRed Hat has rated the issue Critical, saying that RHEL 8, 9 and 10 are affected, along with its own builds of OpenJDK 17, 21 and 25.SiemensSiemens says three of its Industrial Edge Management products are affected.VulnCheckMeanwhile, VulnCheck has made a full RCE exploit available to its customers, and Immersive’s Kevin Breen has reported developing a working exploit.
Products
Atlassian JiraCalif said it achieved unauthenticated remote code execution (RCE) against the default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications.Bambooavailable, Atlassian recommends disabling AVX-512 support as a workaround for the latest versions of Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management Data Center in standard installations.BitbucketAtlassian recommends disabling AVX-512 support as a workaround for the latest versions of Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management Data Center in standard installations.ConfluenceCalif said it achieved unauthenticated remote code execution (RCE) against the default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications.ElasticsearchAccording to Elastic, every Elasticsearch release from 7.17.3 onward is affected.Industrial Edge ManagementSiemens says three of its Industrial Edge Management products are affected.JenkinsCalif said it achieved unauthenticated remote code execution (RCE) against the default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications.Jira Service Management Data Centeras a workaround for the latest versions of Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management Data Center in standard installations.KeycloakCalif said it achieved unauthenticated remote code execution (RCE) against the default configurations of Jira, Confluence, Jenkins, Keycloak and other enterprise applications.LogstashLogstash 8.6.2 and later are also affected, although exploitation requires a specific configuration and can only cause a crash.OpenJDKTracked as CVE-2026-114938, Java4Shell is a memory corruption bug in the way OpenJDK 17.0.6 and newer handle Base64 data.RHELRed Hat has rated the issue Critical, saying that RHEL 8, 9 and 10 are affected, along with its own builds of OpenJDK 17, 21 and 25.
