November 17, 2026: Oracle is shipping fixes for 11 Java SE vulnerabilities today, and every one of them can be exploited over a network without a login. The highest score is 8.1 on CVSS 3.1. The top-scoring one is CVE-2026-114938, now known as Java4Shell, a memory-corruption flaw that Oracle and OpenJDK confirmed later the same day.
Update, November 17, 22:00 UTC: Oracle's full advisory and the OpenJDK advisory now confirm CVE-2026-114938 and list it among the 11 Java fixes. Read our complete technical analysis of Java4Shell for how it works, who is exposed and how to block it before patching.
The Java fixes are part of a much larger release. Oracle's advance notice says its November Critical Security Patch Update carries 652 new security patches across its products. Java SE is a small slice of that, but it is the slice that runs inside almost every enterprise.
What is Oracle fixing in Java this month?
Oracle's advance notice gave the count, the top score and the affected versions:
- Java SE: 8u511 (and 8u511-perf), 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1.
- GraalVM for JDK: 17.0.21 and 21.0.13. GraalVM Enterprise Edition: 21.3.20.0.3.
- JavaFX: 21.0.13, 25.0.5 and 27.0.1.
The replacement builds Oracle has listed are 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. These are targeted security builds, not regular quarterly updates.
That fits Oracle's new rhythm. Since late May, Oracle has shipped smaller monthly security releases between its quarterly Critical Patch Updates, and it calls them Critical Security Patch Updates. The aim is to get urgent fixes out without waiting up to three months. The cost is that admins now have a patch day every month.
What does "remotely exploitable without authentication" mean for Java?
For Java SE, the phrase does not mean someone can hit port 443 and take over the box. It means the vulnerable code can be reached by data an attacker controls, without logging in first. For a server, that is usually input the application parses or deserializes. For a desktop, it is usually untrusted code or content the user opens.
The 8.1 score is also a clue. With no login required, CVSS 3.1 gives 8.1 in two common cases. One is high attack complexity, where the attacker needs specific conditions to line up. The other is user interaction, such as a victim opening a file. A simple, reliable remote code execution with no conditions would score 9.8.
That top issue turned out to be Java4Shell, rated 8.1 with high attack complexity. Its finders have since shown the complexity can be overcome, so treat any Java service that handles input from the internet as exposed.
What is CVE-2026-114938?
It is now known as Java4Shell, and it is the most serious of the 11. Early reports described an unauthenticated remote code execution flaw in OpenJDK 17.0.6 and later, rated 9.2 on CVSS 4.0 by its finders at Calif. Later on November 17, the OpenJDK advisory and Oracle's full advisory confirmed it as a hotspot compiler flaw in Java 17, 21, 25 and 27, rated 8.1 on CVSS 3.1. The CVE record has the official entry.
The bug only triggers on recent x86 server CPUs, Intel Ice Lake and AMD Zen 4 or newer, and ARM servers are safe. Calif says it has working exploits that need no login for Jenkins, Jira, Confluence and Keycloak, but has not released them. No exploitation in the wild has been reported so far.
Who should patch first?
- Internet-facing Java services. API gateways, login and single sign-on services, and anything that processes uploads or tokens before a user signs in.
- Java 17, 21, 25 and 27 on recent Intel and AMD servers. These are exposed to Java4Shell.
- Software that bundles its own runtime. Many commercial products ship a private JDK that system package updates never touch.
- Desktop JavaFX apps that open files or content from outside the organisation.
Java has been here before. December 2021's Log4Shell showed how fast a pre-authentication Java bug can be weaponised, and October's Php2Shell flaws in PHP went from patch to exploitation in days.
How do you find every Java runtime?
The Java you know about is rarely the problem. The risk sits in runtimes nobody tracks: a JDK inside a vendor appliance, an old container base image, or a build server nobody has touched in a year.
A few quick checks catch most of them:
- Servers:
find / -type f -name release -exec grep -l JAVA_VERSION {} + 2>/dev/nulllists every JDK and JRE folder. Eachreleasefile names the vendor and version. - Running services:
ps -eo pid,args | grep [j]avashows the Java binary each process really uses, which is often not the one on your PATH. - Containers:
docker run --rm --entrypoint java IMAGE -versionprints the runtime baked into each image you deploy. - Windows: check installed programs and the Program Files folders of business apps for bundled JREs.
Write down the vendor next to each version. Oracle's November builds only fix Oracle's Java. Java4Shell is in OpenJDK itself, so an Eclipse Temurin or Amazon Corretto runtime needs its own fixed build from its vendor.
What should Java teams do today?
- Use the checks above to list every Java runtime and its vendor, starting with internet-facing services.
- Move Oracle Java SE and GraalVM to the November builds as soon as they are available.
- Restart every service after updating. A running JVM keeps the old code in memory.
- For Temurin, Corretto, Zulu, Red Hat, Microsoft and Linux distribution packages, installing Oracle's builds changes nothing. Java4Shell affects them too, so watch each vendor's security page for its fixed build, and use the stopgap in our Java4Shell analysis until it ships.
- Read Oracle's full advisory for the CVE numbers and affected components, and re-check your priorities against it.
- Until everything is patched, watch internet-facing Java services for unusual errors and unexpected JVM crashes.
Oracle's own products show why patch lag matters. Our Oracle breach timeline and the Oracle company page track incidents where known, fixable flaws were the way in.