Skip to main content
CVE-2026-114938NewsPublished

Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories

Source SecurityWeek

0
Compare
Authoritative record:CVE-2026-114938· High 8.1

Not known to be exploited · CVSS 8.1 High.

Data as of 19 Nov 2026, 09:18 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Oracle CorporationOracle Java SEAffected
  • 8u511b33-perf – 27.0.1.0.3
5 affected builds
Fixed in–
Oracle CorporationOracle GraalVM for JDKAffected
  • =17.0.21.0.3
  • =21.0.13.0.3
Fixed in–
Oracle CorporationOracle GraalVM Enterprise EditionAffected
  • =21.3.20.0.3
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.

References

Community reviews

Loading reviews…