Oracle and the OpenJDK community are set to disclose and patch CVE-2026-114938, an unauthenticated remote code execution flaw reported to affect OpenJDK 17.0.6 and every later Java 17 update, with fixes expected in Oracle’s November Critical Security Patch Update.
CVE-2026-114938 is rated 9.2 (Critical) under CVSS 4.0 and can reportedly be exploited over a network without credentials. Early reports describe the root cause as memory corruption. If the “17.0.6 and later” scope holds, the bug has been present in Java 17 builds since OpenJDK 17.0.6 shipped in January 2023 , which covers almost four years of updates on one of Java’s most widely deployed long-term support releases.
An advisory dated November 16 and attributed to South Korea’s National Cyber Security Center (NCSC) flagged the flaw. According to the report, attackers could run malicious code inside systems without passing a login and urged organisations to begin remediation as soon as the patch is out.
WatchTowr also acknowledged the flaw, and the team was aware of public reports of the flaw under the CVE-2026-114938 identifier and that the details were still unconfirmed.
As of November 17, no Java vendor has published a fixed build or a technical description of CVE-2026-114938, and the CVE record has not been published.
When the CVE-2026-114938 Patch Lands
Korean-language reports put the disclosure at 6 a.m. on Wednesday, November 18, Korea Standard Time. That corresponds to 1 p.m. Pacific time on Tuesday, November 17 (2:30 a.m. Wednesday in India). The pre-release a n nouncement for Oracle’s November 2026 Critical Security Patch Update (CSPU) gives Tuesday, November 17, as the release date but does not give a time of day.
Oracle’s announcement lists 11 new security patches for Java SE. Oracle says all of them may be remotely exploitable without authentication. The highest score in the Java SE section is 8.1 under CVSS 3.1, and Oracle publishes no CVE IDs or per-flaw details before release day.
The affected versions Oracle lists are Java SE 8u511, 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; and JavaFX 21.0.13, 25.0.5 and 27.0.1. Oracle’s own JDK 17.0.21 release notes advise against using that build after the November 17 update. Lens reported that Oracle’s ops.java site listed 17.0.21.1 and 21.0.13.1 as the scheduled Java 17 and Java 21 releases.
Why the Scores Don’t Line Up Yet
The 9.2 rating attached to CVE-2026-114938 is a CVSS 4.0 score, while Oracle scores Java flaws under CVSS 3.1, where its November maximum is 8.1. The two systems weigh exploit conditions differently, so a single bug can score differently under each. Lens cautioned that the published figures cannot be assumed to describe the same vulnerability until Oracle releases its risk matrix.
Oracle’s advance notice also refers only to “Oracle Java SE” and does not mention OpenJDK by name. Reports CVE-2026-114938 so far mention only the Java 17 line. Whether Java 8, 11, 21, 25 and 27 are also affected is not stated in any source Cyber Kendra could reach.
The sources also do not identify the vulnerable component, API or input path, or whether exploitation depends on a particular framework or configuration. A server that runs Java 17 is not necessarily exposed. That depends on whether attacker-controlled data can reach the vulnerable code, which Oracle typically describes in a note on each risk-matrix row.
Is CVE-2026-114938 Being Exploited?
As of November 17, no vendor, government agency, or researcher has reported in-the-wild exploitation of CVE-2026-114938, and no proof-of-concept code has been published. The CVE does not appear in CISA’s Known Exploited Vulnerabilities catalog, which is expected because the record itself is not public yet.
That window may be short. October’s emergency Java alert for CVE-2026-91403 (CVSS 3.1 9.1), which covered compromised eMudhra intermediate certificates, came one day after Oracle’s quarterly update. The PHP2Shell flaws, also rated 9.2 under CVSS 4.0, were reported as exploited within a week of their October 21 patches. Oracle has moved Java to monthly security updates on the third Tuesday of each month, and November’s release is the vehicle for this fix.
Which Java Builds Will Get a Fix
Oracle JDK and GraalVM customers will get fixes through the November CSPU. Downstream OpenJDK builds such as Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat build of OpenJDK, and the openjdk-17 packages in Ubuntu, Debian, RHEL and SUSE ship on their own schedules and with their own version labels. Vendors in the OpenJDK Vulnerability Group usually learn of JDK flaws before disclosure, so same-day releases are common, but no vendor has confirmed a date or build for this fix.
The OpenJDK Vulnerability Group advisory page is where the upstream fixed versions and affected-release matrix will appear. Cyber Kendra will add the fixed build numbers for each distribution to this story when they are published.
What Java Admins Should Do Now
Find every Java 17 runtime before the patch drops, not after. Run java -version on each host, but also check the executable path of running Java processes, because many applications bundle their own JDK. Where permitted, jcmd VM.version reports the exact build of a live JVM. Container images need the same check: look at the base image in each Dockerfile and build pipeline so an old JDK is not reintroduced on the deployment.
Prioritise internet-facing Java services. Lens recommends listing listening ports with ss -lntp and closing unnecessary external exposure, including admin interfaces, with firewalls, security groups and IP allowlists. Lens notes that these steps reduce risk but do not replace patching.
Neither Oracle nor any OpenJDK distributor has published a workaround or configuration change for CVE-2026-114938 . Oracle’s only guidance in the advance notice is to apply the update as soon as possible. After updating, restart the Java processes and confirm that the running build, not just the installed package, is the fixed version.
Join the conversation. Ask questions, solutions, and help others.
Be the first to start the discussion!
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
