CVE-2026-114938: OpenJDK JAVA · Critical Vulnerability
Source Cisco Talos
Not known to be exploited · CVSS 8.1 High.
Data as of 18 Nov 2026, 02:04 UTC
Thin evidence
One scorer or none| CNA (oracle) | CVSS 3.1 | 8.1 |
|---|
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 17 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– |
AI-suggested
A software update addressing this vulnerability is recommended and should be applied when available. If immediate patching is not feasible, a temporary mitigation is to disable AVX-512 support by starting the JVM with the argument "=XX:UseAVX=2" on x86-64 systems. This mitigation is not applicable to ARM-based processors and may cause JVM startup failure on those platforms. Cisco is evaluating its products and will provide updates accordingly. Network detection rules for Snort and Splunk are available to help identify exploitation attempts.
Description
CVE-2026-114938, known as Java4Shell, is a critical vulnerability in OpenJDK Java versions 17.0.6 and later running on x86-64 CPUs with AVX-512 VBMI support enabled. It allows unauthenticated remote code execution triggered by sending malformed Base64 input to affected JVMs. The vulnerability affects processors from Intel and AMD supporting AVX-512 VBMI, impacting both on-premise and cloud environments. No in-the-wild exploitation has been observed yet. Mitigation includes applying software updates or disabling AVX-512 support by starting the JVM with the argument "=XX:UseAVX=2" on x86-64 systems.