Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories
Source SecurityWeek
Not known to be exploited · CVSS 8.1 High.
Data as of 19 Nov 2026, 09:18 UTC
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle CorporationOracle Java SE | Affected
| Fixed in– |
| Oracle CorporationOracle GraalVM for JDK | Affected
| Fixed in– |
| Oracle CorporationOracle GraalVM Enterprise Edition | Affected
| Fixed in– |
Description
Java4Shell (CVE-2026-114938) is a memory corruption vulnerability in OpenJDK 17.0.6 and newer that affects systems with x86-64 processors supporting AVX-512 VBMI. It enables unauthenticated remote code execution (RCE) on default configurations of several enterprise applications, including Jira, Confluence, Jenkins, and Keycloak. Multiple vendors including Cisco, Elastic, Red Hat, and Siemens have confirmed impact on their products and are releasing patches or recommending mitigations. Attackers have begun scanning and attempting exploitation, but no confirmed successful intrusions have been reported yet. Cloud and container customers are advised differently depending on vendor guidance.