11 Java SE fixes
Oracle says all 11 may be exploitable over a network without credentials and gives 8.1 as the highest CVSS 3.1 base score in this group.
Open the Oracle notice ↗Oracle has announced 11 Java SE fixes. The full per-CVE details are still pending in this source snapshot.
Inventory live JVMs, prepare updates, and keep the circulating CVE-2026-114938 claim separate from what Oracle has confirmed.
The advisory is a pre-release announcement. Its values may change when Oracle publishes the full update.
Oracle says all 11 may be exploitable over a network without credentials and gives 8.1 as the highest CVSS 3.1 base score in this group.
Open the Oracle notice ↗The ID and a Java 17 RCE story are circulating. The reviewed Oracle notice does not list the ID or connect it to the 11 fixes.
Read the claim status ↗Start with the runtime that actually serves your application. A version string from a different JVM is not a clearance test.
Identify the distribution and build serving each application. Follow its published security update and replace running instances.
Open patch guideRestrict unnecessary network paths while your teams validate and deploy a vendor fix.
Review controlsJoin service logs, JVM crashes, child processes and outbound connections by host and time.
Open detection guideRead the status of the circulating CVE claim before treating a scanner hit or social post as a verdict.
Review evidenceJava SE, GraalVM and JavaFX have different build rows. An OpenJDK distributor or Linux package vendor needs its own advisory and build evidence.
Oracle’s pre-release statement does not identify the affected components, request path, proof of concept, or individual CVE scores.
Confirm the installed package, container image or appliance update and the version reported by each running JVM after restart.