CVE-2026-114938 in oracle corporation oracle java se
LogPulse has a published detection rule for this CVE: it raises a notable when someone tries to exploit it.
What the vulnerability is
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Compiler). Supported versions that are affected are Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; Oracle GraalVM for JDK: 17.0.21.0.3 and 21.0.13.0.3; Oracle GraalVM Enterprise Edition: 21.3.20.0.3. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
Affected software: oracle corporation oracle java se, oracle corporation oracle graalvm for jdk, oracle corporation oracle graalvm enterprise edition
Scores
- CVSS: 8.1 (high)
- EPSS: No score yet
- CISA KEV: Not listed
- Published: 2026-11-17
What LogPulse has for it
- Detection rule: Yes, published
- Agent check (vulnerable version): No
- Mitigation: No
In the news
4 publications wrote about this CVE in the last 14 days, most recently on 2026-11-17.
- Critical Java4Shell flaw allows RCE attacks on major Java applications (BleepingComputer, 2026-11-17)
- CVE-2026-114938 RCE in OpenJDK: Everything You Need to Know (Wiz, 2026-11-17)
- NCSC-2026-0495 [1.00] [M/H] Kwetsbaarheden verholpen in Oracle Java (NCSC, 2026-11-17)
Source data: NIST NVD, CISA KEV and FIRST EPSS. LogPulse processes new CVEs every hour.
We build every detection with great care, but no two environments are the same. Log sources, parsing and configuration differ, so test a detection in your own environment before you rely on it.