Skip to content
Pre-auth RCE flaw in Java 17 puts servers at risk: affected versions and how to fix (CVE-2026-114938)

Pre-auth RCE flaw in Java 17 puts servers at risk: affected versions and how to fix (CVE-2026-114938)

Aikido.Dev • November 17, 2026

Oracle's November 17, 2026 update includes 11 Java SE patches for flaws that may be exploitable over a network without authentication.

Early reports describe one of them, CVE-2026-114938, as an unauthenticated remote code execution flaw in OpenJDK 17.0.6 and later, rated 9.2 under CVSS 4.0. Oracle has not yet published details.

Oracle lists Java SE 8, 11, 17, 21, 25 and 27 as affected, so patch every Java line you run as soon as fixed builds are available.

To find out if you are affected, click "Am I affected?" on the Aikido dashboard.

Which Java versions and builds are affected?

Oracle's pre-release announcement lists these builds as affected by the vulnerabilities in the November update:

Reports tie CVE-2026-114938 to the Java 17 line only, from OpenJDK 17.0.6 onward. Oracle's list covers all 11 patches.

Treat every Java line you run as in scope until Oracle's risk matrix shows which patch maps to which CVE.

Oracle's notice names Oracle Java SE and does not name OpenJDK. Other builds carry their own version labels and release on their own schedules, so check each vendor's advisory for the fixed build.

Java builds to check:

Oracle Java SE (JDK and JRE)

Oracle GraalVM for JDK and GraalVM Enterprise Edition

OpenJDK builds from other vendors, such as Eclipse Temurin, Amazon Corretto, Azul Zulu, the Microsoft Build of OpenJDK and the Red Hat build of OpenJDK

Linux distribution packages such as openjdk-17

JDKs bundled inside applications and container base images

How to fix CVE-2026-114938

Apply the Java update. Oracle's only guidance is to apply the Critical Security Patch Update as soon as possible. We are not aware of a published workaround or configuration change.

Use your vendor's fixed build. Oracle JDK and GraalVM customers get fixes through the November update. If you run Temurin, Corretto, Zulu or a distribution package, wait for that vendor's fixed version, which may carry a different build number.

Not sure where you run Java? See the section.

Am I affected by CVE-2026-114938?

You are in scope if you run any Java line in the table above. That covers Oracle Java SE, GraalVM, JavaFX and OpenJDK builds from other vendors, including bundled JDKs and container base images.

Running Java does not by itself make a service exploitable. Oracle has not published the vulnerable component or the conditions an attack needs, so exposure depends on whether attacker-controlled input can reach the vulnerable code.

To find out if you are affected, click "Am I affected?" on the Aikido dashboard. It checks your environment for this vulnerability, so you do not need to track down every Java runtime by hand.

Start with internet-facing services. Anything reachable from outside is the likeliest to be hit once details are public.

What is CVE-2026-114938?

Early reports describe CVE-2026-114938 as an unauthenticated remote code execution flaw in OpenJDK 17.0.6 and later, rated 9.2 (Critical) under CVSS 4.0, with memory corruption as the root cause. The reports cite an advisory dated November 16 and attributed to South Korea's National Cyber Security Center (NCSC). If that scope holds, the flaw has been in Java 17 builds since OpenJDK 17.0.6 shipped in January 2023.

What Oracle has confirmed is narrower. Its November 2026 Critical Security Patch Update pre-release announcement confirms 11 Java SE patches that may all be remotely exploitable without authentication, and it publishes no CVE IDs or per-flaw details before release day. As of November 17, the CVE record is not published, no vendor has released a fixed build and no technical description is available, so treat anything beyond Oracle's notice as unconfirmed.

Why the severity scores differ: 9.2 vs 8.1

9.2 is a CVSS 4.0 score. Oracle uses CVSS 3.1, where its highest Java SE score this month is 8.1. The two versions weigh exploit conditions differently, so one bug can score differently in each. For reference, 9.2 under CVSS 4.0 is the same score PHP2Shell carries. The 9.2 flaw and the 8.1 flaw may also be different issues, which Oracle's risk matrix will settle.

If the 8.1 flaw is network-reachable and needs no privileges or user interaction, the usual explanation is high attack complexity. That points to preconditions, such as a specific configuration or a particular way an application passes data to the runtime. This is an inference from the score, and Oracle has not stated it. Running Java 17 does not by itself make a server exploitable, because what matters is whether attacker-controlled input can reach the vulnerable code.

Is CVE-2026-114938 being exploited?

As of November 17, we have seen no reports of exploitation in the wild and no public proof-of-concept code. The CVE record is not published yet, so the flaw is also absent from CISA's Known Exploited Vulnerabilities catalog.

That can change quickly. Once fixed builds ship, the difference between patched and unpatched code is available to anyone who wants to study it, and Oracle strongly recommends applying the fixes as soon as possible. We will update this post when Oracle publishes the advisory and risk matrix, when CVE IDs are matched to the Java SE patches, and if exploitation is reported.

What is CVE-2026-114938? An unauthenticated remote code execution flaw reported in Java 17, rated 9.2 under CVSS 4.0 in early reports. Oracle has not yet published details or confirmed the CVE ID.

Which Java versions are affected by CVE-2026-114938? Reports name OpenJDK 17.0.6 and later. Oracle's pre-release announcement lists Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1 across its 11 Java SE patches. Oracle lists those versions as affected by vulnerabilities in this update, and which versions the specific flaw affects is not confirmed.

When will the Java patch be released? Oracle's November 2026 Critical Security Patch Update is scheduled for Tuesday, November 17, 2026. The pre-release announcement gives no time of day. OpenJDK vendors ship on their own schedules.

Is CVE-2026-114938 being exploited? We have seen no reports of exploitation and no public proof of concept as of November 17.

Why is the CVSS score 9.2 in one place and 8.1 in another? 9.2 is a CVSS 4.0 score from early reports. Oracle's highest Java SE score is 8.1 under CVSS 3.1. The versions score exploit conditions differently, and the two may also describe different flaws.

Is there a workaround? None has been published that we are aware of. Patching is the fix.

How do I know if my Java runtime is vulnerable? Find the distribution, version and build of every Java runtime, including bundled JDKs and container base images, then compare against your vendor's fixed version once it is published.

Get secure today, quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

Extracted Entities

Attack Types (1)