Skip to content
Why SMS Two

Why SMS Two

Cyberkendra •Vivek • November 17, 2026

A critical flaw in Java 17 lets attackers run malicious code on servers without logging in, and full details and patches are due to go public in the early hours of Wednesday, November 18, Korea time.

Tracked as CVE-2026-114938, the vulnerability is rated 9.2 (Critical) under CVSS 4.0. South Korean security industry sources describe it as a memory corruption bug that enables remote code execution (RCE) in Java applications with no authentication required. The flaw is reported to affect OpenJDK 17.0.6 and later, so it reaches back to OpenJDK 17.0.6 in January 2023 and covers almost four years of Java 17 updates.

The first warning came from South Korea. An advisory dated November 16 and attributed to the country’s National Cyber Security Center (NCSC) flagged the flaw, according to Lens , which noted it could not verify the original publication. The NCSC operates under the National Intelligence Service (NIS), which has reportedly told public institutions to audit their Java environments before the disclosure.

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, the CVE record is not yet public, and no attacks have been reported.

Why a Java Flaw Reaches So Far

Java is a runtime as well as a programming language. Code written once runs unchanged on Windows, Linux and other systems, because the Java runtime sits between the program and the operating system. That portability is why Java sits under the server back ends of banks, government agencies, e-commerce platforms and large enterprises.

Java 17 is a long-term support (LTS) release, so many organisations standardised on it and still run it in production. An unauthenticated RCE in the runtime itself, rather than in a single library or app, means an attacker who can reach the vulnerable code path could run commands on the server and get at the data it processes.

When the CVE-2026-114938 Patch Lands

Reports in South Korea put the disclosure, with patches, at 6 a.m. on Wednesday, November 18, Korea Standard Time. That is 1 p.m. Pacific time on Tuesday, November 17, or 2:30 a.m. Wednesday in India. The pre-release announcement for Oracle’s November 2026 Critical Security Patch Update (CSPU) gives Tuesday, November 17, as the release date but no time of day.

Oracle’s announcement lists 11 new security patches for Java SE and says all of them may be remotely exploitable without authentication. The highest Java SE score is 8.1 under CVSS 3.1. Oracle does not publish 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 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 for CVE-2026-114938 is a CVSS 4.0 score. Oracle scores Java flaws under CVSS 3.1, where its November maximum is 8.1. The two systems weigh exploit conditions differently, so one bug can score differently under each, and Lens cautioned that the figures cannot be assumed to describe the same vulnerability until Oracle publishes its risk matrix.

Oracle’s advance notice also refers only to “Oracle Java SE” and does not name OpenJDK. Reports on CVE-2026-114938 so far mention only the Java 17 line. No source Cyber Kendra could reach says whether Java 8, 11, 21, 25 or 27 are also affected.

The vulnerable component, API and input path have not been disclosed, and neither has whether exploitation depends on a particular framework or configuration. Running Java 17 does not by itself make a server exposed. That depends on whether attacker-controlled data can reach the vulnerable code, which Oracle normally explains in a note on each risk-matrix row.

Java’s Rough Autumn: The Flaws Before This One

CVE-2026-114938 lands four weeks after Oracle’s quarterly update on October 20. The OpenJDK advisory for that release covered 53 CVEs, none rated critical, with top scores of 7.5 and 7.0. A 9.2 score puts the new flaw in a different league.

On October 21, Oracle issued an out-of-band security alert for CVE-2026-91403 (CVSS 3.1 9.1) to distrust intermediate certificates tied to the eMudhra compromise. A second alert, CVE-2026-114820, followed on October 24 and removed the associated root certificates from Java’s trust store.

That pair of PHP flaws, CVE-2026-109618 and CVE-2026-109619 , also scored 9.2 under CVSS 4.0, involved memory corruption, and was patched on October 21. Within a week, attackers were running shells on honeypots, and CISA had added both flaws to its Known Exploited Vulnerabilities catalog.

Most Java bugs never get exploited. Waratek counted a record 5,649 Java security flaws published in 2026 , of which attackers had used 18 by November 1. Unauthenticated, network-reachable RCE flaws in widely deployed runtimes are the ones that tend to make that short list.

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 is not in CISA’s KEV catalog, which is expected while the record itself is not yet public.

The PHP2Shell timeline shows how short the gap between patch and attack can be. 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 get fixes through the November CSPU. Downstream OpenJDK builds ship on their own schedules and with their own version labels, including 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. 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.

Upstream fixed versions and the affected-release matrix will appear on the OpenJDK Vulnerability Group advisory page . Cyber Kendra will add fixed build numbers for each distribution to this story as they are published.

What Java Admins Should Do Now

Find every Java 17 runtime before the patch drops. 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. Check container images too: look at the base image in each Dockerfile and build pipeline so an old JDK doesn’t come back with the deployment.

South Korea’s NIS has reportedly given public institutions a preparation checklist. For each Java environment, record the runtime vendor, full build version, operating system, architecture and the person responsible. Review which services are exposed to the internet and block external connections the business does not need. Test product compatibility in advance so the patch can go in as soon as it ships, and set up backup and recovery procedures.

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. 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 so far is to apply the update as soon as possible. After updating, restart the Java processes and confirm 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!